Managed electrical connectivity systems

ABSTRACT

A connector arrangement includes a plug nose body; a printed circuit board positioned within a cavity of the plug nose body; and a plug cover that mounts to the plug nose body to enclose the printed circuit board within the cavity. The printed circuit board includes a storage device configured to store information pertaining to the electrical segment of communications media. The plug cover defines a plurality of slotted openings through which the second contacts are exposed. A connector assembly includes a jack module and a media reading interface configured to receive the plug. A patch panel includes multiple jack modules and multiple media reading interfaces.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional Application Ser.No. 61/252,964, filed Oct. 19, 2009, and titled “Electrical Plug forManaged Connectivity Systems;” and U.S. Provisional Application Ser. No.61/253,208, filed Oct. 20, 2009, and titled “Electrical Plug for ManagedConnectivity Systems,” the disclosures of which are hereby incorporatedherein by reference.

BACKGROUND

In communications infrastructure installations, a variety ofcommunications devices can be used for switching, cross-connecting, andinterconnecting communications signal transmission paths in acommunications network. Some such communications devices are installedin one or more equipment racks to permit organized, high-densityinstallations to be achieved in limited space available for equipment.

Communications devices can be organized into communications networks,which typically include numerous logical communication links betweenvarious items of equipment. Often a single logical communication link isimplemented using several pieces of physical communication media. Forexample, a logical communication link between a computer and aninter-networking device such as a hub or router can be implemented asfollows. A first cable connects the computer to a jack mounted in awall. A second cable connects the wall-mounted jack to a port of a patchpanel, and a third cable connects the inter-networking device to anotherport of a patch panel. A “patch cord” cross connects the two together.In other words, a single logical communication link is often implementedusing several segments of physical communication media.

Network management systems (NMS) are typically aware of logicalcommunication links that exist in a communications network, buttypically do not have information about the specific physical layermedia (e.g., the communications devices, cables, couplers, etc.) thatare used to implement the logical communication links. Indeed, NMSsystems typically do not have the ability to display or otherwiseprovide information about how logical communication links areimplemented at the physical layer level.

SUMMARY

The present disclosure relates to communications connector assembliesand arrangements that provide physical layer management (PLM)capabilities. In accordance with certain aspects, the disclosure relatesto connector arrangements having primary contact arrangements forcommunication signal transmission and secondary contact arrangements formanagement signal transmission.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawings, which are incorporated in and constitute apart of the description, illustrate several aspects of the presentdisclosure. A brief description of the drawings is as follows:

FIG. 1 is a diagram of a portion of an example communications and datamanagement system in accordance with aspects of the present disclosure;

FIG. 2 is a block diagram of one implementation of a communicationsmanagement system that includes PLI functionality as well as PLMfunctionality in accordance with aspects of the present disclosure;

FIG. 3 is a block diagram of one high-level example of a port and mediareading interface that are suitable for use in the management system ofFIG. 2 in accordance with aspects of the present disclosure;

FIGS. 4-14 show an example of a connector arrangement in the form of amodular plug for terminating an electrical communications cable;

FIG. 15 shows one example plug being inserted into an example jackmodule, which is connected to an example media reading interface;

FIGS. 16-23 show an example connector assembly in the form of a jackmodule configured to receive the plug of FIGS. 4-14;

FIGS. 24-29 show an example media reading interface configured toconnect to the jack module of FIGS. 16-23;

FIG. 30 is a perspective view showing a plug inserted within a socket ofa jack module with the bodies of the jack module and media readinginterface substantially removed from view so that the connectionsbetween the various contact members are visible;

FIG. 31 shows one example plug being inserted into an example jackmodule, which is connected to an example media reading interface, wherea main housing of the media reading interface has been removed so thatsecond contacts and a shorting pin are visible;

FIG. 32 is a cross-sectional view of FIG. 30 with the bodies of the jackmodule and media reading interfaces shown;

FIG. 33-51 show a first example patch panel holding one or more jackmodules and media reading interfaces in a single row in accordance withaspects of the present disclosure;

FIGS. 52-60 show a second example patch panel holding one or more jackmodules and media reading interfaces in multiple rows in accordance withaspects of the present disclosure;

FIGS. 61-71 show a third example patch panel holding one or more jackmodules and media reading interfaces in multiple rows in accordance withaspects of the present disclosure; and

FIGS. 72-78 show a fourth example patch panel holding one or more jackmodules and media reading interfaces in multiple rows in accordance withaspects of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 is a diagram of a portion of an example communications and datamanagement system 100. The example system 100 shown in FIG. 1 includes apart of a communications network 101 along which communications signalsS1 pass. In one example implementation, the network 101 can include anInternet Protocol network. In other implementations, however, thecommunications network 101 may include other types of networks.

The communications network 101 includes interconnected networkcomponents (e.g., connector assemblies, inter-networking devices,internet working devices, servers, outlets, and end user equipment(e.g., computers)). In one example implementation, communicationssignals S1 pass from a computer to a wall outlet to a port ofcommunication panel, to a first port of an inter-networking device, outanother port of the inter-networking device, to a port of the same oranother communications panel, to a rack mounted server.

The portion of the communications network 101 shown in FIG. 1 includesfirst and second connector assemblies 130, 130′ at which communicationssignals S1 pass from one portion of the communications network 101 toanother portion of the communications network 101. Non-limiting examplesof connector assemblies 130, 130′ include, for example, rack-mountedconnector assemblies (e.g., patch panels, distribution units, and mediaconverters for fiber and copper physical communication media),wall-mounted connector assemblies (e.g., boxes, jacks, outlets, andmedia converters for fiber and copper physical communication media), andinter-networking devices (e.g., switches, routers, hubs, repeaters,gateways, and access points). In the example shown, the first connectorassembly 130 defines at least one port 132 configured to communicativelycouple at least a first media segment 105 to at least a second mediasegment 115 to enable the communication signals S1 to pass between themedia segments 105, 115.

The at least one port 132 of the first connector assembly 130 may bedirectly connected to a port 132′ of the second connector assembly 130′.As the term is used herein, the port 132 is directly connected to theport 132′ when the communications signals S1 pass between the two ports132, 132′ without passing through an intermediate port. For example,routing a patchcord between port 132 and port 132′ directly connects theports 132, 132′.

The port 132 of the first connector assembly 130 also may be indirectlyconnected to the port 132′ of the second connector assembly 130′. As theterm is used herein, the port 132 is indirectly connected to the port132′ when the communications signals S1 pass through an intermediateport when traveling between the ports 132, 132′. For example, in oneimplementation, the communications signals S1 may be routed over onemedia segment from the port 132 at the first connector assembly 130 to aport of a third connector assembly at which the media segment is coupledto another media segment that is routed from the port of the thirdconnector assembly to the port 132′ of the second connector assembly130′.

Non-limiting examples of media segments include optical fibers, whichcarry optical data signals, and electrical conductors (e.g., CAT-5, 6,and 7 twisted-pair cables), which carry electrical data signals. Mediasegments also can include electrical plugs, fiber optic connectors(e.g., SC, LC, FC, LX.5, or MPO connectors), adapters, media converters,and other physical components terminating to the fibers, conductors, orother such media segments. The techniques described here also can beused with other types of connectors including, for example, BNCconnectors, F connectors, DSX jacks and plugs, bantam jacks and plugs.

In the example shown, each media segment 105, 115 is terminated at aplug or connector 110, 120, respectively, which is configured tocommunicatively connect the media segments 105, 115. For example, in oneimplementation, the port 132 of the connector assembly 130 can beconfigured to align ferrules of two fiber optic connectors 110, 120. Inanother implementation, the port 132 of the connector assembly 130 canbe configured to electrically connect an electrical plug with anelectrical socket (e.g., a jack). In yet another implementation, theport 132 can include a media converter configured to connect an opticalfiber to an electrical conductor.

In accordance with some aspects, the connector assembly 130 does notactively manage (e.g., is passive with respect to) the communicationssignals S1 passing through port 132. For example, in someimplementations, the connector assembly 130 does not modify thecommunications signal S1 carried over the media segments 105, 115.Further, in some implementations, the connector assembly 130 does notread, store, or analyze the communications signal S1 carried over themedia segments 105, 115.

In accordance with aspects of the disclosure, the communications anddata management system 100 also provides physical layer information(PLI) functionality as well as physical layer management (PLM)functionality. As the term is used herein, “PLI functionality” refers tothe ability of a physical component or system to identify or otherwiseassociate physical layer information with some or all of the physicalcomponents used to implement the physical layer of the system. As theterm is used herein, “PLM functionality” refers to the ability of acomponent or system to manipulate or to enable others to manipulate thephysical components used to implement the physical layer of the system(e.g., to track what is connected to each component, to traceconnections that are made using the components, or to provide visualindications to a user at a selected component).

As the term is used herein, “physical layer information” refers toinformation about the identity, attributes, and/or status of thephysical components used to implement the physical layer of thecommunications system 101. In accordance with some aspects, physicallayer information of the communications system 101 can include mediainformation, device information, and location information.

As the term is used herein, “media information” refers to physical layerinformation pertaining to cables, plugs, connectors, and other suchmedia segments. In accordance with some aspects, the media informationis stored on or in the media segments, themselves. In accordance withother aspects, the media information can be stored at one or more datarepositories for the communications system, either alternatively or inaddition to the media, themselves. Non-limiting examples of mediainformation include a part number, a serial number, a plug or otherconnector type, a conductor or fiber type, a cable or fiber length,cable polarity, a cable or fiber pass-through capacity, a date ofmanufacture, a manufacturing lot number, information about one or morevisual attributes of physical communication media (e.g., informationabout the color or shape of the physical communication media or an imageof the physical communication media), and an insertion count (i.e., arecord of the number of times the media segment has been connected toanother media segment or network component). Media information also caninclude testing or media quality or performance information. The testingor media quality or performance information, for example, can be theresults of testing that is performed when a particular segment of mediais manufactured.

As the term is used herein, “device information” refers to physicallayer information pertaining to the communications panels,inter-networking devices, media converters, computers, servers, walloutlets, and other physical communications devices to which the mediasegments attach. In accordance with some aspects, the device informationis stored on or in the devices, themselves. In accordance with otheraspects, the device information can be stored at one or more datarepositories for the communications system, either alternatively or inaddition to the devices, themselves. Non-limiting examples of deviceinformation include a device identifier, a device type, port prioritydata (that associates a priority level with each port), and port updates(described in more detail herein).

As the term is used herein, “location information” refers to physicallayer information pertaining to a physical layout of a building orbuildings in which the network 101 is deployed. Location informationalso can include information indicating where each communicationsdevice, media segment, network component, or other component that isphysically located within the building. In accordance with some aspects,the location information of each system component is stored on or in therespective component. In accordance with other aspects, the locationinformation can be stored at one or more data repositories for thecommunications system, either alternatively or in addition to the systemcomponents, themselves.

In accordance with some aspects, one or more of the components of thecommunications network 101 is configured to store physical layerinformation pertaining to the component as will be disclosed in moredetail herein. In FIG. 1, the connectors 110, 120, the media segments105, 115, and/or the connector assemblies 130, 130′ may store physicallayer information. For example, in FIG. 1, each connector 110, 120 maystore information pertaining to itself (e.g., type of connector, data ofmanufacture, etc.) and/or to the respective media segment 105, 115(e.g., type of media, test results, etc.).

In another example implementation, the media segments 105, 115 orconnectors 110, 120 may store media information that includes a count ofthe number of times that the media segment (or connector) has beeninserted into port 132. In such an example, the count stored in or onthe media segment is updated each time the segment (or plug orconnector) is inserted into port 132. This insertion count value can beused, for example, for warranty purposes (e.g., to determine if theconnector has been inserted more than the number of times specified inthe warranty) or for security purposes (e.g., to detect unauthorizedinsertions of the physical communication media).

In accordance with certain aspects, one or more of the components of thecommunications network 101 also can read the physical layer informationfrom one or more media segments retained thereat. In certainimplementations, one or more network components includes a media readinginterface that is configured to read physical layer information storedon or in the media segments or connectors attached thereto. For example,in one implementation, the connector assembly 130 includes a mediareading interface 134 that can read media information stored on themedia cables 105, 115 retained within the port 132. In anotherimplementation, the media reading interface 134 can read mediainformation stored on the connectors or plugs 110, 120 terminating thecables 105, 115, respectively.

In some implementations, some types of physical layer information can beobtained by the connector assembly 130 from a user at the connectorassembly 130 via a user interface (e.g., a keypad, a scanner, a touchscreen, buttons, etc.). The connector assembly 130 can provide thephysical layer information obtained from the user to other devices orsystems that are coupled to the network 101 (as described in more detailherein). In other implementations, some or all physical layerinformation can be obtained by the connector assembly 130 from otherdevices or systems that are coupled to the network 101. For example,physical layer information pertaining to media that is not configured tostore such information can be entered manually into another device orsystem that is coupled to the network 101 (e.g., at the connectorassembly 130, at the computer 160, or at the aggregation point 150).

In some implementations, some types of non-physical layer information(e.g., network information) can be obtained by one network componentfrom other devices or systems that are coupled to the network 101. Forexample, the connector assembly 130 may pull non-physical layerinformation from one or more components of the network 101. In otherimplementations, the non-physical layer information can be obtained bythe connector assembly 130 from a user at the connector assembly 130.

In accordance with some aspects of the disclosure, the physical layerinformation read by a network component may be processed or stored atthe component. For example, in certain implementations, the firstconnector assembly 130 shown in FIG. 1 is configured to read physicallayer information stored on the connectors 110, 120 and/or on the mediasegments 105, 115 using media reading interface 134. Accordingly, inFIG. 1, the first connector assembly 130 may store not only physicallayer information about itself (e.g., the total number of availableports at that assembly 130, the number of ports currently in use, etc.),but also physical layer information about the connectors 110, 120inserted at the ports and/or about the media segments 105, 115 attachedto the connectors 110, 120.

In some implementations, the connector assembly 130 is configured toadd, delete, and/or change the physical layer information stored in oron the segment of physical communication media 105, 115 (i.e., or theassociated connectors 110, 120). For example, in some implementations,the media information stored in or on the segment of physicalcommunication media 105, 115 can be updated to include the results oftesting that is performed when a segment of physical media is installedor otherwise checked. In other implementations, such testing informationis supplied to the aggregation point 150 for storage and/or processing.In some implementations, modification of the physical layer informationdoes not affect the communications signals S1 passing through theconnector assembly 130.

In other implementations, the physical layer information obtained by themedia reading interface (e.g., interface 134 of FIG. 1) may becommunicated (see PLI signals S2) over the network 101 for processingand/or storage. The components of the communications network 101 areconnected to one or more aggregation devices 150 (described in greaterdetail herein) and/or to one or more computing systems 160. For example,in the implementation shown in FIG. 1, each connector assembly 130includes a PLI port 136 that is separate from the “normal” ports 132 ofthe connector assembly 130. Physical layer information is communicatedbetween the connector assembly 130 and the network 101 through the PLIport 136. In the example shown in FIG. 1, the connector assembly 130 isconnected to a representative aggregation device 150, a representativecomputing system 160, and to other components of the network 101 (seelooped arrow) via the PLI port 136.

The physical layer information is communicated over the network 101 justlike any other data that is communicated over the network 101, while atthe same time not affecting the communication signals S1 that passthrough the connector assembly 130 on the normal ports 132. Indeed, insome implementations, the physical layer information may be communicatedas one or more of the communication signals S1 that pass through thenormal ports 132 of the connector assemblies 130, 130′. For example, inone implementation, a media segment may be routed between the PLI port136 and one of the “normal” ports 132. In such an implementation, thephysical layer information may be passed along the communicationsnetwork 101 to other components of the communications network 101 (e.g.,to the one or more aggregation points 150 and/or to the one or morecomputer systems 160). By using the network 101 to communicate physicallayer information pertaining to it, an entirely separate network neednot be provided and maintained in order to communicate such physicallayer information.

In other implementations, however, the communications network 101includes a data network along which the physical layer informationdescribed above is communicated. At least some of the media segments andother components of the data network may be separate from those of thecommunications network 101 to which such physical layer informationpertains. For example, in some implementations, the first connectorassembly 130 may include a plurality of fiber optic adapters definingports at which connectorized optical fibers are optically coupledtogether to create an optical path for communications signals S1. Thefirst connector assembly 130 also may include one or more electricalcable ports at which the physical layer information (see PLI signals S2)are passed to other parts of the data network. (e.g., to the one or moreaggregation points 150 and/or to the one or more computer systems 160).

FIG. 2 is a block diagram of one example implementation of acommunications management system 200 that includes PLI functionality aswell as PLM functionality. The management system 200 comprises aplurality of connector assemblies 202. The system 200 includes one ormore connector assemblies 202 connected to an IP network 218. Theconnector assemblies 202 shown in FIG. 2 illustrate variousimplementations of the connector assembly 130 of FIG. 1.

Each connector assembly 202 includes one or more ports 204, each ofwhich is used to connect two or more segments of physical communicationmedia to one another (e.g., to implement a portion of a logicalcommunication link for communication signals S1 of FIG. 1). At leastsome of the connector assemblies 202 are designed for use with segmentsof physical communication media that have physical layer informationstored in or on them. The physical layer information is stored in or onthe segment of physical communication media in a manner that enables thestored information, when the segment is attached to a port 204, to beread by a programmable processor 206 associated with the connectorassembly 202.

In the particular implementation shown in FIG. 2, each of the ports 204of the connector assemblies 202 comprises a respective media readinginterface 208 via which the respective programmable processor 206 isable to determine if a physical communication media segment is attachedto that port 204 and, if one is, to read the physical layer informationstored in or on the attached segment (if such media information isstored therein or thereon). The programmable processor 206 associatedwith each connector assembly 202 is communicatively coupled to each ofthe media reading interfaces 208 using a suitable bus or otherinterconnect (not shown).

In the particular implementation shown in FIG. 2, four example types ofconnector assembly configurations are shown. In the first connectorassembly configuration 210 shown in FIG. 2, each connector assembly 202includes its own respective programmable processor 206 and its ownrespective network interface 216 that is used to communicatively couplethat connector assembly 202 to an Internet Protocol (IP) network 218.

In the second type of connector assembly configuration 212, a group ofconnector assemblies 202 are physically located near each other (e.g.,in a bay or equipment closet). Each of the connector assemblies 202 inthe group includes its own respective programmable processor 206.However, in the second connector assembly configuration 212, some of theconnector assemblies 202 (referred to here as “interfaced connectorassemblies”) include their own respective network interfaces 216 whilesome of the connector assemblies 202 (referred to here as“non-interfaced connector assemblies”) do not. The non-interfacedconnector assemblies 202 are communicatively coupled to one or more ofthe interfaced connector assemblies 202 in the group via localconnections. In this way, the non-interfaced connector assemblies 202are communicatively coupled to the IP network 218 via the networkinterface 216 included in one or more of the interfaced connectorassemblies 202 in the group. In the second type of connector assemblyconfiguration 212, the total number of network interfaces 216 used tocouple the connector assemblies 202 to the IP network 218 can bereduced. Moreover, in the particular implementation shown in FIG. 2, thenon-interfaced connector assemblies 202 are connected to the interfacedconnector assembly 202 using a daisy chain topology (though othertopologies can be used in other implementations and embodiments).

In the third type of connector assembly configuration 214, a group ofconnector assemblies 202 are physically located near each other (e.g.,within a bay or equipment closet). Some of the connector assemblies 202in the group (also referred to here as “master” connector assemblies202) include both their own programmable processors 206 and networkinterfaces 216, while some of the connector assemblies 202 (alsoreferred to here as “slave” connector assemblies 202) do not includetheir own programmable processors 206 or network interfaces 216. Each ofthe slave connector assemblies 202 is communicatively coupled to one ormore of the master connector assemblies 202 in the group via one or morelocal connections. The programmable processor 206 in each of the masterconnector assemblies 202 is able to carry out the PLM functions for boththe master connector assembly 202 of which it is a part and any slaveconnector assemblies 202 to which the master connector assembly 202 isconnected via the local connections. As a result, the cost associatedwith the slave connector assemblies 202 can be reduced. In theparticular implementation shown in FIG. 2, the slave connectorassemblies 202 are connected to a master connector assembly 202 in astar topology (though other topologies can be used in otherimplementations and embodiments).

Each programmable processor 206 is configured to execute software orfirmware that causes the programmable processor 206 to carry out variousfunctions described below. Each programmable processor 206 also includessuitable memory (not shown) that is coupled to the programmableprocessor 206 for storing program instructions and data. In general, theprogrammable processor 206 determines if a physical communication mediasegment is attached to a port 204 with which that processor 206 isassociated and, if one is, to read the identifier and attributeinformation stored in or on the attached physical communication mediasegment (if the segment includes such information stored therein orthereon) using the associated media reading interface 208.

In the fourth type of connector assembly configuration 215, a group ofconnector assemblies 202 are housed within a common chassis or otherenclosure. Each of the connector assemblies 202 in the configuration 215includes their own programmable processors 206. In the context of thisconfiguration 215, the programmable processors 206 in each of theconnector assemblies are “slave” processors 206. Each of the slaveprogrammable processor 206 is also communicatively coupled to a common“master” programmable processor 217 (e.g., over a backplane included inthe chassis or enclosure). The master programmable processor 217 iscoupled to a network interface 216 that is used to communicativelycouple the master programmable processor 217 to the IP network 218.

In this configuration 215, each slave programmable processor 206 isconfigured to determine if physical communication media segments areattached to its port 204 and to read the physical layer informationstored in or on the attached physical communication media segments (ifthe attached segments have such information stored therein or thereon)using the associated media reading interfaces 208. The physical layerinformation is communicated from the slave programmable processor 206 ineach of the connector assemblies 202 in the chassis to the masterprocessor 217. The master processor 217 is configured to handle theprocessing associated with communicating the physical layer informationread from by the slave processors 206 to devices that are coupled to theIP network 218.

The system 200 includes functionality that enables the physical layerinformation that the connector assemblies 202 capture to be used byapplication-layer functionality outside of the traditionalphysical-layer management application domain. That is, the physicallayer information is not retained in a PLM “island” used only for PLMpurposes but is instead made available to other applications. In theparticular implementation shown in FIG. 2, the management system 200includes an aggregation point 220 that is communicatively coupled to theconnector assemblies 202 via the IP network 218.

The aggregation point 220 includes functionality that obtains physicallayer information from the connector assemblies 202 (and other devices)and stores the physical layer information in a data store. Theaggregation point 220 can be used to receive physical layer informationfrom various types of connector assemblies 202 that have functionalityfor automatically reading information stored in or on the segment ofphysical communication media. Also, the aggregation point 220 andaggregation functionality 224 can be used to receive physical layerinformation from other types of devices that have functionality forautomatically reading information stored in or on the segment ofphysical communication media. Examples of such devices include end-userdevices—such as computers, peripherals (e.g., printers, copiers, storagedevices, and scanners), and IP telephones—that include functionality forautomatically reading information stored in or on the segment ofphysical communication media.

The aggregation point 220 also can be used to obtain other types ofphysical layer information. For example, in this implementation, theaggregation point 220 also obtains information about physicalcommunication media segments that is not otherwise automaticallycommunicated to an aggregation point 220. This information can beprovided to the aggregation point 220, for example, by manually enteringsuch information into a file (e.g., a spreadsheet) and then uploadingthe file to the aggregation point 220 (e.g., using a web browser) inconnection with the initial installation of each of the various items.Such information can also, for example, be directly entered using a userinterface provided by the aggregation point 220 (e.g., using a webbrowser).

The aggregation point 220 also includes functionality that provides aninterface for external devices or entities to access the physical layerinformation maintained by the aggregation point 220. This access caninclude retrieving information from the aggregation point 220 as well assupplying information to the aggregation point 220. In thisimplementation, the aggregation point 220 is implemented as “middleware”that is able to provide such external devices and entities withtransparent and convenient access to the PLI maintained by the accesspoint 220. Because the aggregation point 220 aggregates PLI from therelevant devices on the IP network 218 and provides external devices andentities with access to such PLI, the external devices and entities donot need to individually interact with all of the devices in the IPnetwork 218 that provide PLI, nor do such devices need to have thecapacity to respond to requests from such external devices and entities.

For example, as shown in FIG. 2, a network management system (NMS) 230includes PLI functionality 232 that is configured to retrieve physicallayer information from the aggregation point 220 and provide it to theother parts of the NMS 230 for use thereby. The NMS 230 uses theretrieved physical layer information to perform one or more networkmanagement functions. The NMS 230 communicates with the aggregationpoint 220 over the IP network 218.

As shown in FIG. 2, an application 234 executing on a computer 236 canalso use the API implemented by the aggregation point 220 to access thePLI information maintained by the aggregation point 220 (e.g., toretrieve such information from the aggregation point 220 and/or tosupply such information to the aggregation point 220). The computer 236is coupled to the IP network 218 and accesses the aggregation point 220over the IP network 218.

In the example shown in FIG. 2, one or more inter-networking devices 238used to implement the IP network 218 include physical layer information(PLI) functionality 240. The PLI functionality 240 of theinter-networking device 238 is configured to retrieve physical layerinformation from the aggregation point 220 and use the retrievedphysical layer information to perform one or more inter-networkingfunctions. Examples of inter-networking functions include Layer 1, Layer2, and Layer 3 (of the OSI model) inter-networking functions such as therouting, switching, repeating, bridging, and grooming of communicationtraffic that is received at the inter-networking device.

The aggregation point 220 can be implemented on a standalone networknode (e.g., a standalone computer running appropriate software) or canbe integrated along with other network functionality (e.g., integratedwith an element management system or network management system or othernetwork server or network element). Moreover, the functionality of theaggregation point 220 can be distribute across many nodes and devices inthe network and/or implemented, for example, in a hierarchical manner(e.g., with many levels of aggregation points). The IP network 218 caninclude one or more local area networks and/or wide area networks (e.g.,the Internet). As a result, the aggregation point 220, NMS 230, andcomputer 236 need not be located at the same site as each other or atthe same site as the connector assemblies 202 or the inter-networkingdevices 238.

Also, power can be supplied to the connector assemblies 202 usingconventional “Power over Ethernet” techniques specified in the IEEE802.3af standard, which is hereby incorporated herein by reference. Insuch an implementation, a power hub 242 or other power supplying device(located near or incorporated into an inter-networking device that iscoupled to each connector assembly 202) injects DC power onto one ormore of the wires (also referred to here as the “power wires”) includedin the copper twisted-pair cable used to connect each connector assembly202 to the associated inter-networking device.

FIG. 3 is a schematic diagram of one example connection system 300including a connector assembly 320 configured to collect physical layerinformation from a connector arrangement 310. The example connectionsystem 300 shown includes a jack module 320 and an electrical plug 310.The connector arrangement 310 terminates at least a first electricalsegment (e.g., a conductor cable) 305 of physical communications mediaand the connector assembly 320 terminates at least second electricalsegments (e.g., twisted pairs of copper wires) 329 of physicalcommunications media. The connector assembly 320 defines at least onesocket port 325 in which the connector arrangement 310 can beaccommodated.

Each electrical segment 305 of the connector arrangement 310 carriescommunication signals (e.g., communications signals S1 of FIG. 1) toprimary contact members 312 on the connector arrangement 310. Theconnector assembly 320 includes a primary contact arrangement 322 thatis accessible from the socket port 325. The primary contact arrangement322 is aligned with and configured to interface with the primary contactmembers 312 to receive the communications signals (S1 of FIG. 1) fromthe primary contact members 312 when the connector arrangement 310 isinserted into the socket 325 of the connector assembly 320.

The connector assembly 320 is electrically coupled to one or moreprinted circuit boards. For example, the connector assembly 320 cansupport or enclose a first printed circuit board 326, which connects toinsulation displacement contacts (IDCs) 327 or to another type ofelectrical contacts. The IDCs 327 terminate the electrical segments 329of physical communications media (e.g., conductive wires). The firstprinted circuit board 326 manages the primary communication signalscarried from the conductors terminating the cable 305 to the electricalsegments 329 that couple to the IDCs 327.

In accordance with some aspects, the connector arrangement 310 caninclude a storage device 315 configured to store physical layerinformation. The connector arrangement 310 also includes second contactmembers 314 that are electrically coupled (i.e., or otherwisecommunicatively coupled) to the storage device 315. In oneimplementation, the storage device 315 is implemented using an EEPROM(e.g., a PCB surface-mount EEPROM). In other implementations, thestorage device 315 is implemented using other non-volatile memorydevice. Each storage device 315 is arranged and configured so that itdoes not interfere or interact with the communications signalscommunicated over the media segment 305.

The connector assembly 320 also includes a second contact arrangement(e.g., a media reading interface) 324. In certain implementations, themedia reading interface 324 is accessible through the socket port 325.The second contact arrangement 324 is aligned with and configured tointerface with the second contact members 314 of the media segment toreceive the physical layer information from the storage device 315 whenthe connector arrangement 310 is inserted into the socket 325 of theconnector assembly 320.

In some such implementations, the storage device interfaces 314 and themedia reading interfaces 324 each comprise three (3) leads—a power lead,a ground lead, and a data lead. The three leads of the storage deviceinterface 314 come into electrical contact with three (3) correspondingleads of the media reading interface 324 when the corresponding mediasegment is inserted in the corresponding port 325. In certain exampleimplementations, a two-line interface is used with a simple charge pump.In still other implementations, additional leads can be provided (e.g.,for potential future applications). Accordingly, the storage deviceinterfaces 314 and the media reading interfaces 324 may each includefour (4) leads, five (5) leads, six (6) leads, etc.

The storage device 315 also may include a processor or micro-controller,in addition to the storage for the physical layer information. In someexample implementations, the micro-controller can be used to executesoftware or firmware that, for example, performs an integrity test onthe cable 305 (e.g., by performing a capacitance or impedance test onthe sheathing or insulator that surrounds the cable 305, (which mayinclude a metallic foil or metallic filler for such purposes)). In theevent that a problem with the integrity of the cable 305 is detected,the micro-controller can communicate that fact to a programmableprocessor (e.g., processor 206 of FIG. 2) associated with the port usingthe storage device interface (e.g., by raising an interrupt). Themicro-controller also can be used for other functions.

The connector assembly 320 also can support or enclose a second printedcircuit board 328, which connects to the second contact arrangement 324.The second printed circuit board 328 manages the physical layerinformation communicated from a storage device 315 through secondcontacts 314, 324. In the example shown, the second printed circuitboard 328 is positioned on an opposite side of the connector assembly320 from the first printed circuit board 326. In other implementations,the printed circuit boards 326, 328 can be positioned on the same sideor on different sides. In one implementation, the second printed circuitboard 328 is positioned horizontally relative to the connector assembly320 (see FIG. 3). In another implementation, the second printed circuitboard 328 is positioned vertically relative to the connector assembly320.

The second printed circuit board 328 can be communicatively connected toone or more programmable electronic processors and/or one or morenetwork interfaces. In one implementation, one or more such processorsand interfaces can be arranged as components on the printed circuitboard 328. In another implementation, one of more such processor andinterfaces can be arranged on a separate circuit board that is coupledto the second printed circuit board 328. For example, the second printedcircuit board 328 can couple to other circuit boards via a card edgetype connection, a connector-to-connector type connection, a cableconnection, etc. The network interface is configured to send thephysical layer information to the data network (e.g., see signals S2 ofFIG. 1).

FIGS. 4-78 provide example implementations of physical layer managementnetworks and components for electrical (e.g., copper) communicationsapplications. FIGS. 4-14 show an example of a connector arrangement 5000in the form of a modular plug 5002 for terminating an electricalcommunications cable 5090. The connector arrangement 5000 is configuredto be received within a port of a connector assembly as will bedescribed in more detail herein. In accordance with one aspect, theconnector arrangement 5000 includes a plug 5002, such as an RJ plug,that connects to the end of an electrical segment of communicationsmedia, such as twisted pair copper cable 5090.

The plug 5002 includes a wire manager 5008 for managing the twisted wirepairs and a strain relief boot 5010, which snaps to the plug 5002 (seeFIGS. 4 and 5). For example, the plug 5002 defines openings 5005 inwhich lugs 5009 on the wire manager 5008 can latch (see FIG. 13). FIGS.12-14 show details of one example wire manager 5008 and boot 5010suitable for use with the plug 5002. In the example shown, the wiremanager 5008 and boot 5010 are integrally formed. A first portion 5008Aof the wire manager 5008 is connected to a second portion 5008B with aliving hinge. In other implementations, however, other types of wiremanagers and boots may be utilized.

The plug 5002 also includes a plug nose body 5004 having a first side5014 and a second side 5016 (FIGS. 6-11). In one embodiment, a shield5003 can be mounted to the plug nose body 5004. For example, the shield5003 can be snap-fit to the plug nose body 5004. The first side 5014 ofthe plug nose body 5004 includes a key member 5015 and a finger tab 5050that extends outwardly from the key member 5015. The key member 5015 andfinger tab 5050 facilitates aligning and securing the connectorarrangement 5000 to a connector assembly as will be described in moredetail herein. In certain implementations, the finger tab 5050 attachesto the plug nose body 5004 at the key member 5015. In oneimplementation, the finger tab 5050 and the key member 5015 are unitarywith the plug nose body 5004.

The finger tab 5050 is sufficiently resilient to enable a distal end5051 of the finger tab 5050 to flex or pivot toward and away from theplug nose body 5004. Certain types of finger tabs 5050 include at leastone cam follower surface 5052 and a latch surface 5054 for latching tothe connector assembly as will be described in more detail herein. Incertain implementations, the finger tab 5050 includes two cam followersurfaces 5052 located on either side of a handle extension 5053 (seeFIG. 6). Depressing the handle extension 5053 moves the latch surfaces5054 toward the plug nose body 5004. In certain implementations, thewire manager 5008 and/or boot 5010 include a flexible grip surface 5011that curves over at least the distal end 5051 of the handle extension5053 to facilitate depressing of the handle extension 5053 (e.g., seeFIG. 4).

The second side 5016 of the plug nose body 5004 is configured to holdmain signal contacts 5012, which are electrically connected to thetwisted pair conductors of the communications cable. Ribs 5013 protectthe main signal contacts 5012. In the example shown, the plug 5002 isinsertable into a port of a mating jack of a connector assembly, such asport 325 of jack module 320 of FIG. 3. The main signal contacts 5012 ofthe plug 5002 electrically connect to contacts positioned in the jackmodule to create an electrical path over which communications signals,such as signals S1 of FIG. 1, are carried. In accordance with otheraspects, however, the connector arrangement 5000 can define other typesof electrical connections.

In some implementations, the key member 5015 of the plug nose body 5004defines a cavity 5060 (see FIG. 6). In accordance with some aspects, thekey member 5015 is positioned at a front of the plug nose body 5004. Inthe example shown, the key member 5015 forms the base 5052 of the fingertab 5050. The key member 5015 includes support members 5016 that definesguide grooves 5017 in the interior sides of the housing member 5015.

The connector arrangement 5000 also includes a storage device 5030 (FIG.7) that is configured to store information (e.g., an identifier and/orattribute information) pertaining to the segment of physicalcommunications media (e.g., the plug 5002 and/or the electrical cableterminated thereat). In some embodiments, the connector arrangement 5000also can include additional components to aid in physical layermanagement. In some embodiments, the storage device 5030 can be arrangedon a printed circuit board 5020 that is mounted to the modular plug 5002(see FIGS. 8-9). In the example shown, the printed circuit board 5020can be slid along the guide grooves 5017 within the cavity 5060 definedby the housing member 5015. In certain embodiments, additionalcomponents can be arranged on the printed circuit board 5020.

In the example shown in FIGS. 6-7, the printed circuit board 5020includes a substrate with conductive traces electrically connectingcontacts and lands. The circuit 5020 also includes circuit components,including the media storage device 5030, at the lands. In the exampleshown in FIG. 7, the circuit 5020 includes an EEPROM 5032. In oneembodiment, the EEPROM 5032 forms the media storage device 5030 formodular plug 5002. In other embodiments, however, the storage device5030 can include any suitable type of memory.

In accordance with some aspects, the circuit 5020 defines a body 5022having a first side 5021 and a second side 5023. The EEPROM 5032 can bemounted to the second side 5023 of the PCB body 5022. The circuitcontacts 5034 are arranged on the first side 5023 of the PCB body 5022.The circuit contacts 5034 permit connection of the EEPROM 5032 to amedia reading interface, such as media reading interface 324 of FIG. 3.

The plug 5002 also includes a plug cover 5006 that mounts on the plugnose body 5004 (see FIGS. 8-9). In the example shown, the plug cover5006 mounts to the housing member 5015 to enclose the cavity 5060. Forexample, the plug cover 5006 includes a body 5040 defining a first side5042 and a second side 5044. In the example shown, the first side 5042is generally orthogonal to the second side 5044. Ribs 5046 extendbetween the first and second sides 5042, 5044. In the example shown, theribs 5046 extend over a curved edge defined by the first and secondsides 5042, 5044. In one example, contacts of a media reading interfaceon a patch panel can extend through the ribs 5046 to connect to thecircuit contacts 5034 on the printed circuit board 5020.

The body 5040 of the plug cover 5006 can define latch arms 5007configured to latch within the cavity 5060 defined in the housing member5015. For example, the latch arms 5007 can latch behind the supportmembers 5016 defined in the cavity 5060. In the example shown, the latcharms 5007 are configured to extend beneath the printed circuit board5020 when the board 5020 is mounted within the guiding grooves 5017 inthe cavity 5060. In one implementation, the plug cover 5006 fitsgenerally flush with the housing member 5015 when the printed circuitboard 5020 is mounted within the housing member 5015 (see FIGS. 10-11)

In accordance with some aspects, the connector arrangement ismanufactured by fabricating a plug body 5004 including a key member5015, mounting a storage device 5030 within a cavity 5060 of the keymember 5015, and closing the cavity 5060 with a cover member 5006. Insome implementations, fabricating the plug body 5004 includes moldingthe plug body 5004 with the cavity 5060 in the key member 5015. In otherimplementations, fabricating the plug body 5004 includes molding theplug body 5004 with the key member 5015 and subsequently eliminating(e.g., cutting, melting, disintegrating, etc.) material in the keymember 5015 to form the cavity 5060.

In some implementations, the storage device 5030 is manufactured bymounting an EEPROM chip 5032 on a printed circuit board 5020. Contacts5034 also are mounted to the printed circuit board 5020 to beelectrically connected to the EEPROM chip 5032 via tracings of theprinted circuit board 5020. In certain implementations, the EEPROM 5032is mounted to one side of the printed circuit board and the contacts5034 are mounted to a different (e.g., opposite) side.

In some implementations, positioning the storage device 5030 within theplug cavity 5060 includes sliding the storage device 5030 along guides5017 formed in the cavity 5060. In certain implementations, mounting thestorage device 5030 within the cavity 5060 including positioning thestorage device 5030 within the cavity 5060 with the contact pads 5034outwardly from the plug body 5004 and the EEPROM 5032 facing inwardlytoward the plug body 5004. In certain implementations, closing thecavity 5060 of the plug 5002 includes latching the cover member 5006 toinner surfaces of the key member 5015.

FIG. 15 shows one example connector arrangement 5000 (e.g., plug 5002)being inserted into an example connector assembly 5100. The exampleconnector assembly 5100 shown includes a jack module 5110 defining asocket 5112 that is configured to receive the plug 5002. In oneimplementation, the jack module 5110 includes an RJ-45 jack socket 5112.In other implementations, the jack module 5110 may include another typeof jack socket.

FIGS. 16-23 illustrate one example jack module 5110 that is suitable foruse with the plug 5002 disclosed herein. The jack module 5110 alsodefines slots 5119 through which plug connection contacts 5141 extendinto the socket 5112. The plug connection contacts 5141 define contactsurfaces 5142 at which the plug connection contacts 5141 contact themain signal contacts 5012 of the plug 5002. The jack module 5110 definesa guide surface 5114 within the socket 5112 that the plug 5002 followswhen inserted into the jack module 5110 (FIG. 17). The guide surface5114 leads to a stop surface 5115 within the socket 5112 that abutsagainst a front end of the plug 5002 when the plug 5002 is inserted.

Certain types of jack modules 5110 also include latching members 5116that retain the plug 5002 within the socket 5112 when the plug 5002 isinserted (see FIG. 17). In some implementations, the latching members5116 having a first end defining a cam surface 5117 and a second enddefining a shoulder 5118 (FIG. 19). When the plug 5002 is inserted intothe socket 5112, the cam follower surfaces 5052 on the finger tab 5050of the plug 5002 ride over the cam surface 5117 of the latching member5116 of the jack module 5110. When the plug 5002 has been sufficientlyinserted, the latch surfaces 5054 of the finger tab 5050 snap behind theshoulders 5118 of the latching members 5116 of the jack module 5110.

The latching members 5116 retain the plug 5002 within the socket 5112and guard against unintentional removal of the plug 5002 from the socket5112. To remove the plug 5002 from the socket 5112, a user may depressthe handle extension 5053 of the finger tab 5050 to flex the finger tab5050 toward the plug nose body 5004. For example, the user may push onthe flexible grip surface 5011 on the plug 5002, which presses on thehandle extension 5053 of the finger tab 5050. Flexing the finger tab5050 toward the plug nose body 5004 lifts the latch surfaces 5054 out ofalignment with the shoulders 5118 of the latching members 5116 of thejack module 5110, thereby allowing a user to pull the plug 5002 out ofthe socket 5112.

In certain types of jack modules 5110, the plug connection contacts 5141of the jack module 5110 are configured to electrically couple to one ormore insulation displacement contacts (IDCs) 5144 located at an IDCsection 5121 of the jack module 5110 (see FIG. 32). Inserting the plug5002 into the socket 5112 brings the main signal contacts 5012 of theplug 5002 into contact with the contact surfaces 5142 of the plugconnection contacts 5141, thereby establishing an electrical connectiontherebetween. Signals carried by the media segments terminated at theplug 5002 may be transferred to media segments terminated at the IDCs5144 via the plug main signal contacts 5012 of the jack module 5110. Inother implementations, however, the plug connection contacts 5141 mayconnect to other types of contacts, such as plug contacts of anotherjack module, or to other electrical components.

In some implementations, the plug connection contacts 5141 connectdirectly to the IDCs 5144. For example, in one implementation, the plugconnection contacts 5141 and the IDCs 5144 may form a unitary contactmember. In other implementations, the plug connection contacts 5141connect to the IDCs 5144 via a first printed circuit board 5143. Forexample, in one implementation, the plug connection contacts 5141 andthe IDCs 5144 may connect to the printed circuit board 5143 using solderpins, using a surface mount connection, or using another type ofconnection (see FIG. 32). Certain types of jack modules 5110 includes aseat 5120 configured to support the first printed circuit board 5143. Inthe example shown in FIG. 32, the first printed circuit board 5143extends in a plane that is parallel to the insertion axis of the plug5002.

In some implementations, the jack module 5110 also includes a strainrelief member 5130 that aids in retaining a second electrical cable atthe jack module 5110. In particular, the strain relief member 5130 aidsin retaining a second electrical cable having electrical conductors(e.g., wires) terminated at the IDCs 5144 of the jack module 5110.Certain types of strain relief members 5130 include a support surface5131 connected to at least one arm 5132 having a latching tab 5133 thatconnects to the jack module 5110. In the example shown in FIGS. 18, 19,and 21, the example strain relief member 5130 includes a curved supportsurface 5131 extending between two arms 5132, each arm 5132 defining alatching tab 5133.

The jack module 5110 defines at least one rib 5129 at which the latchingtab 5133 of the strain relief member 5130 may latch. In the exampleshown, the jack module 5110 defines multiple ribs 5129 at each side ofthe jack module 5110. The strain relief device 5130 may be adjusted toaccommodate various types and sizes of second cables by latching thetabs 5133 of the strain relief device 5130 to appropriate ribs 5129. Incertain implementations, the strain relief device 5130 defines a springclip such that outward pressure applied to the support member 5131causes the arms 5132 to flex toward the sides of the jack module 5110,thereby strengthening the force with which the strain relief device 5130attaches to the jack module 5110. In one implementation, the supportmember 5131 defines one or more protrusions, cutouts, bumps, or othersurface texturing members that aid in retaining the cable against thesupport member 5131 (e.g., see FIG. 18).

In some implementations, the jack module 5110 includes a second section5138 that couples to the first section 5111. In certain implementations,the first section 5111 defines the socket 5112, the latching members5116, and the IDC section 5121. In such implementations, the secondsection 5138 may cover at least the IDC section 5121 of the firstsection 5111 to protect the conductor terminations at the IDCs 5144. Forexample, certain types of second sections 5138 include a base 5139 thatextends across the IDC section 5121 and arms 5140 that extend over sidesof the jack module 5110 (FIG. 16). The arms 5140 of the second section5138 may latch or otherwise attach to the first section 5111 of the jackmodule 5110. In some implementations, the first section 5111 defines theribs 5129 to which the strain relief member 5130 attaches. In otherimplementations, however, the second section 5138 may define the ribs5129.

In some implementations, an electrically conductive shield 5134 may beinstalled (e.g., snap-fit, clipped, latched, etc.) on the jack module5110 (FIG. 17). For example, the shield 5134 may be used to ground thejack module 5110 and electrical segments connected therein. In theexample shown, the conductive shield 5134 includes a first section 5135that extends over a first side of the jack module 5110 and side sections5136 that extend over the sides of the jack module 5110. In certainimplementations, the shield 5134 includes wrap-around sections 5137 thatwrap around the front of the jack module 5110 and extend at leastpartially into the socket 5112. The wrap-around sections 5137 areconfigured to contact the shield 5003 of the plug 5002 when the plug5002 is inserted in the jack module 5110. In one implementation, thewrap-around sections 5137 define a resilient section to aid in makingcontact with the plug shield 5003.

Certain types of jack modules 5110 are configured to mount to a patchpanel as will be described in more detail herein. In someimplementations, the jack module 5110 includes guides 5122 that aid ininstalling the jack module 5110 in an example patch panel. In theexample shown in FIGS. 16-23, the guides 5122 define wing extensionshaving ramped or camming surfaces at a first end. In one implementation,the jack module 5110 includes a guide 5122 extending outwardly from eachside of the jack module 5110 (FIGS. 20-21). In one implementation, theguides 5122 are formed on the first section 5111 of the jack module5110.

Certain types of jack modules 5110 also may include a panel latchingarrangement 5123 to aid in securing the jack module 5110 to a patchpanel. In some implementations, the panel latching arrangement 5123includes at least a first latch member having a ramped surface 5124 anda shoulder 5125. In the example shown, the panel latching arrangement5123 includes two latch members separated by a gap 5126. Each latchmember defines a ramped surface 5124 at one end and a shoulder 5125 atthe opposite end. In certain implementations, the latch members aregenerally located between the guides 5122. In certain implementations,the panel latching arrangement 5123 is located on the first section 5111of the jack module 5110.

Referring back to FIG. 15, the connector assembly 5100 also includes amedia reading interface 5145 (FIGS. 24-29) coupled to the jack module5110. The media reading interface 5145 includes a second set of contacts5146 that are configured to contact the storage device contacts 5034 ofthe plug 5002 (e.g., see FIG. 30) to provide a conductive path betweenthe storage device contacts 5034 and a data network, such as network 101of FIG. 1 or network 218 of FIG. 2. In certain implementations, thesecond contacts 5146 connect to a second printed circuit board 5165 (seeFIG. 32) that is configured to connect to the data network (e.g., via aprocessor and/or network interface as described herein).

In accordance with some aspects, at least portions of the secondcontacts 5146 of the media reading interface 5145 extend into the socket5112 of the jack module 5110. In some implementations, the portions ofthe second contacts 5146 may extend through a cutout 5113 defined in asurface of the jack module 5110 (see FIG. 31). The cutout 5113 providesaccess to the jack socket 5112 through a wall of the jack module 5110.In some implementations, the cutout 5113 is continuous with a socketport at the front of the jack module 5110. In certain implementations,the cutout 5113 may be located at an opposite side of the jack module5110 from the contact slots 5119 through which the plug connectioncontacts 5141 extend into the socket 5112 (e.g., see FIG. 15). Forexample, in one implementation, the cutout 5113 is located on the sameside of the jack module 5110 as the latching members 5116 for securingthe plug 5002 (e.g., see FIG. 31).

Certain types of jack modules 5110 may include guide members 5127 (seeFIGS. 16, 19, and 20) that aid in securing the media reading interface5145 to the jack module 5110. In the example shown in FIG. 16, the guidemembers 5127 are located on either side of the cutout 5113. In otherimplementations, the guide members 5127 may be located elsewhere on thejack module 5110. In some implementations, the guide members 5127 definechannels 5128 (FIG. 20) that are configured to receive portions of themedia reading interface 5145 (e.g., see FIG. 15).

One example media reading interface 5145 is shown in FIGS. 24-29. Theexample media reading interface 5145 is suitable for use with the jackmodule 5110 shown in FIGS. 16-23. The media reading interface 5145includes guide flanges 5151 (FIG. 24) that are sized and shaped to bereceived within the channels 5128 of the guide members 5127 of the jackmodule 5110. In one implementation, the guide flanges 5151 include stops(e.g., bumps) 5152 that aid in securing the media reading interface 5145to the guide members 5127 of the jack module 5110 (see FIG. 24). Forexample, the stops 5152 may be defined at forward ends of the guideflanges 5151.

In some implementations, the media reading interface 5145 also includesa stop arrangement 5163. In the example shown in FIG. 24, the stoparrangement 5163 defines a generally U-shaped upward extension includinglaterally extending wings that define guide channels on either side ofthe stop 5163. In some implementations, the media reading interface 5145is mounted to the jack module 5110 by sliding the guide flanges 5151 ofthe media reading interface 5145 into the guide channels 5128 of thejack module 5110. In certain implementations, the stop 5163 of the mediareading interface 5145 defines wings that ride over the camming surfacesof the latching members 5116 of the jack module 5110 when the mediareading interface 5145 is inserted.

The example media reading interface 5145 also defines a channel 5150(FIGS. 25 and 29) configured to receive a second printed circuit board5165, which connects to a data network. For example, the second printedcircuit board 5165 may connect to a processor (e.g., a slave processoror a master processor) and/or to a network interface for connection tothe data network. In certain implementations, the second printed circuitboard 5165 extends in a plane that is generally orthogonal to theinsertion axis of the plug 5002 into the socket 5112. In oneimplementation, the second printed circuit board 5165 extends in a planethat is generally orthogonal to the first printed circuit board 5143.

As shown in FIGS. 26 and 27, the second contacts 5146 include one ormore contact members that extend from first sections defining plugcontact surfaces 5147 to second sections defining PCB contact surfaces5148. The plug contact surfaces 5147 of the second contacts 5146 extendout of the media reading interface 5145, through the cutout 5113 of thejack module 5110, and into the jack socket 5112. The PCB contactsurfaces extend into the channel 5150 to contact the second printedcircuit board 5165 (see FIG. 25). In certain implementations, the secondsections of the second contacts 5146 curve around in a J-shape to alignthe PCB contact surfaces 5148 with the second circuit board 5165 withinthe channel 5150.

In certain implementations, the media reading interface 5145 includes afirst housing part 5156 and a second housing part 5160. The secondcontacts 5146 are held between the first and second housing parts 5156,5160. In some implementations, the channel 5150 for the second circuitboard 5165 is formed in the first housing part 5156. In otherimplementations, the channel 5150 is formed in the second housing part5160. In still other implementations, the first and second housing parts5156, 5160 cooperate to form the channel 5150 (e.g., see FIG. 32). Insome implementations, the first housing part 5156 defines a viewingchannel 5153 that forms a passage between the PCB channel 5150 and anexterior of the media reading interface 5145. The viewing channel 5153is configured to align with a light indicator (e.g., an LED) 5169installed on the second printed circuit board 5165 (e.g., see FIG. 42).

In some implementations, the first housing part 5156 forms a mainhousing and the second housing part 5160 defines a retention section.The first housing part 5156 defines the PCB channel 5150 extendingbetween front and rear flanges. The viewing channel 5153 extends throughthe front flange. The rear flange defines a passage 5158 in which thesecond housing part 5160 may be received. In certain implementations,one of the housing parts 5156, 5160 defines alignment members and theother of the housing parts 5156, 5160 defines alignment slots to aid inassembling the media reading interface 5146 (e.g., see FIG. 26).

Further, in certain implementations, one of the housing parts 5156, 5160defines slots in which the contact members of the second contacts 5146may be received. For example, in some implementations, the first housingpart 5156 defines slots 5157 that receive the contact members of thesecond contacts 5146. Indeed, in some implementations, the secondhousing part 5160 includes ribs 5161 that aid in spacing the contactmembers of the second contacts 5146 and inhibit touching of the contactmembers. The slots 5157 of the first housing part 5156 align withchannels between the ribs 5161 of the second housing part 5160.

In some implementations, the second contacts 5146 form spring contacts.In some such implementations, the first sections are configured to flextoward the stop 5163 when a plug 5002 presses against the plug contactsurfaces 5147. For example, the first sections may pass through thechannels defined between the ribs 5161. In certain implementations, thestop 5163 defines a ramped surface 5164 facing the second contacts 5146.The ramped surface 5164 may be shaped and positioned to accommodateflexing of the second contacts 5146 when a plug 5002 is inserted intothe jack 5110.

In some implementations, the second housing part 5160 is configured tolatch to the first housing part 5156. For example, in someimplementations, the second housing part includes one or more latchmembers 5162 that are configured to latch to latching recesses 5159 ofthe first housing part 5156. In one implementation, each latch member5162 defines a ramped surface and an opposite facing shoulder (FIGS.26-27). In other implementations, the latch members may be defined onthe first housing part 5156 and the latching recesses may be defined onthe second housing part 5160. In still other implementations, the secondhousing part 5160 may be otherwise secured to the first housing part5156.

In accordance with some aspects, certain types of media readinginterfaces 5145 are configured to aid in determining whether a plug 5002has been received in the socket 5112 of the jack module 5110. In someimplementations, the media reading interface 5145 includes a sensingmember that interacts with at least some of the second contacts 5146. Inother implementations, the media reading interface 5145 includes ashorting pin 5155 that extends across at least two contact members ofthe second contacts 5146 (see FIGS. 28 and 31).

At least some of the contact members of the second contacts 5146 defineshorting surfaces 5149 that are configured to selectively contact theshorting pin 5155. The shorting pin 5155 causes an electrical shortbetween two or more contact members of the second contacts 5146 when theshorting surfaces 5149 of the contact members touch the shorting pin5155. The second printed circuit board 5165 is configured to determinewhether the contact members are shorted together.

In some implementations, the media reading interface 5145 defines a pinreceiving passage 5154 (FIGS. 27-29) in which the shorting pin 5155 maybe received. In some implementations, the pin receiving passage 5154 isdefined in the first housing part 5156. In certain implementations, thepassage 5154 extends across two contact member slots 5157 of the firsthousing 5156. In other implementations, the passage 5154 extends crossall contact members slots 5157 of the first housing part 5156. In stillother implementations, the pin receiving passage 5154 may be defined inthe second housing part 5160.

As shown in FIG. 32, when the plug 5002 is received in the socket 5112of the jack module 5110, the main signal contacts 5012 touch the plugconnection contacts 5141 and the storage member contacts 5034 touch theplug contact surfaces 5147 of the second contacts. The key member 5015of the plug 5002 pushes the first sections of the second contacts 5146downwardly (see FIG. 30). Depressing the plug contact surfaces 5147 ofthe second contacts 5146 pulls the shorting surfaces 5149 away from theshorting pin 5155 (see FIG. 32), thereby eliminating the electricalshort between the contact members.

Referring to FIGS. 33-78, in accordance with some aspects, one or morejack modules 5110 and media reading interfaces 5145 can be coupledtogether to form patch panels. In general, the patch panels have fronts,rears, first sides, and second sides. The fronts of the patch panelsdefines multiple front ports at which to receive plugs (e.g., plug 5002of FIGS. 4-14) that terminate electrical cables. The rears of the patchpanels define multiple rear terminations at which additional electricalcables may be received and terminated. In some implementations, the rearterminations include fixed terminations, such as insulation displacementcontacts. For example, in certain implementations, the sockets 5112 ofthe jack modules 5110 define the front ports and the IDCs 5144 of thejack modules 5110 define the rear terminations. In otherimplementations, the rear terminations may include additional jackmodules or other types of connectors.

FIGS. 33-51 show a first example patch panel 5200 having a front 5201, arear 5202, a first side 5203, and a second side 5204. The patch panel5200 is configured to hold at least one jack module (e.g., jack module5110 of FIGS. 16-23) and at least one media reading interface (e.g.,media reading interface 5145 of FIGS. 24-29). The front 5201 of thefirst example patch panel 5200 defines one or more front ports 5205through which the sockets of the jack modules are accessible. The rear5202 of the first example patch panel 5200 includes rear terminationsdefined by the IDS section 5121 of the jack modules.

The patch panel 5200 includes mounting members 5206 that are configuredto enable installation of the patch panel 5200 to a rack, frame,cabinet, or other equipment structure. In certain implementations, themounting members 5206 are located at the sides 5203, 5204 of the patchpanel 5200. In the example shown, the mounting members 5206 defineopenings 5207 through which fasteners (e.g., screws, bolts, rivets,etc.) may extend to secure the patch panel 5200 to one or more rails.

In some implementations, the patch panel 5200 includes a front housingpart 5210 and a rear housing part 5220 (see FIG. 34). The first housingpart 5210 defines the front ports 5205. In some implementations, thefront housing part 5210 includes a frame 5240. In certainimplementations, the front housing part 5210 also includes a fascia 5250that is removeably coupled to the frame 5240. In certainimplementations, the patch panel 5200 also includes a groundingconnection 5209 (FIG. 35). The grounding connection 5209 may connect tothe shields 5134 of the jack modules 5110 and/or to the second printedcircuit board 5165.

The rear housing part 5220 includes at least one or more jack modules5110 mounted to a chassis 5230. In certain implementations, the rearhousing part 5220 also includes one or more media reading interfaces5145. In one implementation, the patch panel 5200 has the same number ofjack modules 5110 and media reading interfaces 5145. In otherimplementations, the patch panel 5200 has more jack modules 5110 thanmedia reading interfaces 5145. For example, in one implementation, thepatch panel 5200 may have twice as many jack modules 5110 than mediareading interfaces 5145. In other implementations, the patch panel 5200may include more media reading interfaces 5145 than jack modules 5110.For example, in certain implementations, each jack module 5110 maydefine two plug sockets. In such implementations, each plug socket mayhave its own media reading interface 5145.

In some implementations, the media reading interfaces 5145 are mountedto a printed circuit board 5165. In the example shown in FIG. 34,multiple media reading interfaces 5145 mount over at least a first edgeof the second printed circuit board 5165. Each media reading interface5145 also is connected to at least one jack module 5110. The secondprinted circuit board 5165 in installed at the patch panel 5200. Forexample, in FIG. 34, the second printed circuit board 5165 is configuredto be held between the first housing part 5210 and the second housingpart 5220.

In some implementations, the first housing part 5210 is fastened to thesecond housing part 5220. In the example shown, the frame 5240 definesone or more first openings 5212, the second printed circuit board 5165defines one or more second openings 5222, and the chassis 5230 definesone or more third openings 5224. One or more fasteners (e.g., screws,bolts, etc.) 5215 are configured to extend through the first, second,and third openings 5212, 5222, 5224 to secure the second printed circuitboard 5165 between the frame 5240 and the chassis 5230. In certainimplementations, the fastener 5215 is configured to extend through aspacer 5218 positioned between the frame 5240 and the second printedcircuit board 5165.

In the example shown, a threaded fastener 5215 is configured to extendthrough the openings 5212, 5222, 5224. In some implementations, thethreaded fastener 5215 is configured to screw directly into the chassis5230 (e.g., into the passages 5224 defined in the chassis 5230). Inother implementations, however, the threaded fastener 5215 is configuredto screw into a threaded insert 5225. In some such implementations, thethreaded insert 5225 may abut against a portion of the chassis 5230 froma rear of the chassis 5230. For example, the threaded insert 5225 maymount at least partially within the passage 5224 defined in the chassis5230 and abut against a forward or intermediate surface of the chassis5230. Of course, any of these attachment mechanisms can be used on thecomponents of any of the patch panels disclosed herein.

The patch panel 5200 may be configured to receive a processing unit(e.g., a CPU) 5270. In generally, the processing unit 5270 includes atleast one processor (e.g., processor 206 or processor 217 of FIG. 2).For example, the second printed circuit board 5165 may define aconnector or connector port (e.g., see FIG. 57) that connects to aconnector port or connector 5271 on the processing unit 5270. The secondprinted circuit board 5165 electrically connects the media readinginterfaces 5145 to the processing unit 5270. Accordingly, the processingunit 5270 may request one or more of the media reading interfaces 5145to read information (e.g., physical layer information) from the storagedevice 5030 of one or more corresponding plugs 5002. The processing unit5270 also may receive the information from the media reading interfaces5145 and provide the information to a data network (e.g., network 101 ofFIG. 1 or network 218 of FIG. 2). In certain implementations, theprocessing unit 5270 also may provide (e.g., write) information to thestorage device 5030 of one or more plugs 5002 via the media readinginterfaces 5145.

In some implementations, the patch panel 5200 also may include at leastone cable manager 5260. In certain implementations, the patch panel 5200includes a cable manager 5260 that organizes the cables connected to therear terminations. In some implementations, the cable manager 5260mounts to the second housing part 5220. For example, in oneimplementation, the cable manager 5260 mounts to the chassis 5230. Inanother implementation, the cable manager mounts to the groundingassembly 5209 (e.g., see FIG. 52) that mounts to the chassis 5230. Inother implementations, the cable manager 5206 may mount to the fronthousing part 5210.

One example implementation of a frame 5240 is shown in FIG. 34B. Theframe 5240 includes a frame body 5241 defining at least one opening 5242through which a plug 5002 can access a socket 5112 of a jack module5110. In certain implementations, the openings 5242 are sufficientlylarge to enable the front of both the jack module 5110 and the mediareading interface 5145 to be viewing from a front of the frame 5240 whenthe first and second housing parts 5210, 5220 are mounted together. Forexample, the viewing channel 5153 of the media reading interface 5145may be viewing through the frame opening 5242.

In certain implementations, the frame body 5241 defines upper and lowerbent flanges 5243 that wrap around portions of the second housing part5220 to aid in retaining the first and second housing parts 5210, 5220.In certain implementations, the lower flange 5243 may aid in retainingthe second printed circuit board 5165 within the patch panel 5200. Forexample, the lower bent flange 5243 of the frame body 5241 may extendover a bottom of the second circuit board 5165 to hold the secondcircuit board 5165 within the channel 5150 defined in the second mediareading interface (e.g., see FIG. 51)

As noted above, the frame body 5241 also defines openings 5212 throughwhich fasteners (e.g., screws, bolts, rivets, etc.) 5215 may be insertedto secure the first housing part 5210 to the second housing part 5220.In some implementations, the frame body 5241 also defines openings toaccommodate components mounted to the second housing part 5220. Forexample, the frame body 5241 may define openings 5246, 5247 toaccommodate a cable port 5166 and light indicators 5167, respectively,as will be described in more detail herein.

In some implementations, the frame body 5241 defines the mountingmembers 5206. For example, side flanges of the frame 5241 define theopenings 5207 through which fasteners may be extended. In otherimplementations, separate mounting members 5206 may connect to the framebody 5241. In other implementations, the mounting members 5206 may bedefined by the fascia 5250. In still other implementations, the mountingmembers 5206 may connect to the second housing part 5220 (e.g., to thechassis 5230).

The frame body 5241 also is configured to receive the fascia 5250. Insome implementations, the frame body 5241 defines openings 5244configured to receive retaining members 5258 of the fascia 5250. Inother implementations, the frame body 5241 may define retaining membersthat fit into openings defined in the fascia 5250. In certainimplementations, the frame body 5241 also includes tabs 5245 that extendforwardly from some of the openings 5242 to be received in slots definedin the fascia 5250 to aid in aligning and installing the fascia 5250 onthe frame 5240.

One example implementation of a fascia 5250 is shown in FIG. 34A. Thefascia 5250 includes a fascia body 5251 defining a plurality of openings5252 that align with the openings 5242 of the frame body 5241 to provideaccess to the jack module socket 5112 from the front 5201 of the patchpanel 5200. In some implementations, the openings 5252 of the fasciabody 5251 are smaller than the openings 5242 of the frame body 5241. Incertain implementations, the openings 5252 of the fascia body 5251define keyways 5253 for the plugs 5002. They keyways 5253 of the fasciabody 5251 are oriented to align with the cutouts 5113 of the jackmodules 5110 when the first and second housing parts 5210, 5220 aremounted together.

In some implementations, the fascia body 5251 includes tabs 5254 thatextend rearwardly from the fascia body 5251. In the example shown, thetabs 5254 generally align with the openings 5252. In otherimplementations, however, the fascia body 5251 may include greater orfewer tabs 5254. The tabs 5254 extend over the upper and lower bendflanges 5243 of the frame body 5241 when the fascia 5250 is mounted tothe frame 5240. In one implementation, the tabs 5254 friction-fit overthe flanges 5243 of the frame to aid in retaining the fascia 5250 to theframe 5240. In certain implementations, some of the tabs 5254 defineopenings, cutouts 5255, or inner protrusions that may aid in retainingthe fascia 5250 to the frame 5240.

As noted above, the fascia body 5251 also includes retaining members5258 to secure the fascia body 5251 to the frame body 5241. In someimplementations, the fascia body 5251 includes at least one retainingmember 5258 at each side of the fascia body 5251. In otherimplementations, the fascia body 5251 includes multiple retainingmembers 5258 at each side of the fascia body 5251. In still otherimplementations, the fascia body 5251 includes multiple retainingmembers spaced along at least one side (e.g., a bottom) of the fasciabody 5251.

In some implementations, the retaining members 5258 extend through theframe body 5241 and latch in the openings 5244. In otherimplementations, the retaining members 5258 may otherwise secure (e.g.,latch, press-fit, snap-fit, etc.) to the frame body 5241 via latchingopenings 5244. In other implementations, the retaining members 5258 mayextend through the openings 5244 and secure to the chassis 5230 of thesecond housing part 5220.

In some implementations, the fascia body 5251 also defines openings toaccommodate components mounted to the second housing part 5220. Forexample, the fascia body 5251 may define openings 5256, 5257, 5259 toaccommodate a cable port 5166 and light indicators 5167 of the secondprinted circuit board 5165. One example implementation of a printedcircuit board 5165 including a cable port 5166 and light indicators 5167will be described in more detail herein.

As shown in FIGS. 37-39, end caps 5280 may be mounted over the sideflanges of the frame 5241 to cover the mounting members 5206. In theexample shown, each end cap 5280 includes a body 5281 that is sized andshaped to cover the front of one side flange of the frame 5241. Each endcap 5280 also includes mounting members 5282 by which the end cap body5281 is attached to the patch panel 5200. In some implementations, themounting members 5282 attach to the frame body 5241. In otherimplementations, the mounting members 5282 attach to the fascia body5251.

Certain types of end caps 5280 are configured to pivot to selectivelyexpose and cover the openings 5207 of the mounting members 5206. In someimplementations, the mounting members 5282 include pins about which theend cap body 5281 may pivot (FIG. 39). In the example shown in FIG. 37,the mounting pins 5282 attach to sides of the fascia body 5251. The endcap 5280 also includes a retention mechanism 5283 (FIG. 39) by which theend cap body 5281 may be retained in position to cover the mountingmember openings 5207. The retention mechanism 5283 grips a portion 5287(FIG. 37) of the mounting member 5206 when the end cap 5280 covers themounting member 5206. In the example shown, the retention mechanism 5283includes flanges 5284 and latching tab 5285 that extend through cutouts5286 defined in the mounting member. The latching tab 5285 snaps behindthe portion 5287 of the mounting member 5206.

Labels may be installed on the fascia body 5251. In someimplementations, labels are installed on a front of the fascia body5251. For example, labels may be glued, latched, or otherwise secured toa front of the fascia body 5251. In other implementations, however,labels may be installed behind a clear or opaque fascia body 5251. Incertain implementations, one or more label holders 5290 may be mountedto first part 5210 of the patch panel 5200.

One example label holder 5290 is shown in FIGS. 40 and 41. The examplelabel holder 5290 includes a holder body 5291 having a first side 5298and a second side 5299. At least the first side 5298 of the holder body5291 defines a tray 5292 bounded by upper and lower flanges 5293. One ormore labels may be seated in the tray 5292 between the flanges 5293. Incertain implementations, retention tabs 5296 (FIG. 41) may be providedto further aid in retaining the labels within the tray 5292. In certainimplementations, the label holder 5290 may include dividing flanges 5297(FIG. 41) that separate sections of the holder tray 5292 to facilitatemounting multiple labels to the tray 5292 side-by-side.

In some implementations, the label holder 5290 is configured to mountbetween the frame body 5241 and the fascia body 5251. For example, incertain implementations, the holder body 5291 includes a firstattachment end 5294 and a second attachment end 5295 that are heldbetween the frame and fascia bodies 5241, 5251 (e.g., see FIGS. 36 and36A). In the example shown, at least the second attachment end 5295 isconfigured to extend through an opening 5259 in the fascia body 5251(see FIG. 36A).

Certain types of label holders 5290 are configured to be reversible. Forexample, the label holder 5290 shown in FIGS. 40-41 includes flanges5293 that extend both forwardly and rearwardly from the tray 5292.Accordingly, labels may be seated at the tray 5292 on either side 5298,5299 of the label holder 5290. In one implementation, the first side5298 (FIG. 40) of the label holder 5290 is configured to hold oneelongated label and the second side 5299 (FIG. 41) of the label holder5290 is configured to hold multiple shorter labels. The first and secondattachment ends 5294, 5295 of the holder body 5291 are configured sothat the label holder 5290 may be secured to the first housing part 5210with either the first side 5298 or the second side 5299 facing forwardlythrough the fascia body 5251. Accordingly, a user may select which sideof the label holder 5290 to utilize to holder labels.

FIGS. 42-49 show example components of the second housing part 5220.FIG. 42 is a front perspective view of one example second housing part5220 mounted to a first edge of the second printed circuit board 5165. Afront side of the second printed circuit board 5165 defines contact pads5168 at which the second contacts 5146 of the media reading interface5145 electrically connect to the second circuit board 5165 (see FIG.43). The rear side of the second printed circuit board 5165 includes aconnector or connector 5278 (FIG. 57) that is configured to couple to aconnector or connector port 5271 (FIG. 34) of the processing unit 5270.

The front side of the second circuit board 5165 also includes a lightindicator (e.g., an light emitting diode) 5169 that is used to displayinformation pertaining to the media reading interface 5145, the secondcontacts 5146, the jack module 5110, and/or the plug connection contacts5141 (see FIG. 43). The light is visible through the viewing channel5153 of the media reading interface 5145. In some implementations, thesecond printed circuit board 5165 also may include additional lightindicators 5167 to provide information to a user about the status of thepatch panel (see FIG. 42). For example, the additional light indicators5167 may provide error information. In the example shown in FIG. 42, thesecond printed circuit board 5165 includes three additional lightindicators 5167. In other implementations, however, the second printedcircuit board 5165 may include greater or fewer additional lightindicators 5167.

In certain implementations, the second circuit board 5165 also includesa cable port 5166 at which a cable may be interfaced to the secondprinted circuit board 5165 (e.g., see FIG. 42). For example, the cableport 5166 may enable a user to connect a data cable to the secondprinted circuit board 5165 to obtain information from the storage device5030 on one or more plugs 5002 inserted in the patch panel 5200. Incertain implementations, the cable port 5166 also may enable a user towrite information directly to the storage device 5030 of one or moreplugs 5002. In other implementations, the cable port 5166 enables a userto access the processing unit 5270 from the front 5201 of the patchpanel 5200.

One example chassis 5230 is shown in FIGS. 45-48. The chassis 5230includes a chassis body 5231 defining openings 5232 through which thejack modules 5110 can be mounted to the chassis body 5231. In theexample shown, the chassis body 5231 defines a recess 5235 (FIGS. 45-46)through which the processing unit 5270 may extend to connect to thesecond printed circuit board 5165. In certain implementations, thechassis body 5231 includes a mounting member 5233 extending into eachopening 5232 (see FIGS. 43-44). In the example shown, each mountingmember 5233 includes a generally T-shaped body defining channels 5234 oneither side. Each mounting member 5233 is configured to aid in retainingone of the jack modules 5110 in the opening 5232.

In certain implementations, the jack modules 5110 are installed on thechassis body 5231 from the rear side of the chassis body 5231 (e.g., seeFIG. 42). The jack module 5110 slides into the opening 5232 with theguide members 5127 of the jack module 5110 (see FIGS. 17 and 19)positioned on either side of the mounting member 5233. In oneimplementation, the latching members 5116 of the jack module 5110 slidewithin the channels 5234 defined by the mounting member 5233 (see FIGS.43-44).

In some implementations, each media reading interface 5145 is mounted toa corresponding jack module 5110 after the jack module 5110 is mountedto the chassis body 5231. In other implementations, each media readinginterface 5145 is installed on the second printed circuit board 5165 toform a board arrangement 5289 (FIG. 49). The board arrangement 5289 canbe mounted to the chassis body 5231 before or after the jack modules5110 are mounted to the chassis body 5231 (e.g., see FIG. 43).

In some implementations, the chassis body 5231 includes one or morelatching members 5236 that aid in retaining the jack modules 5110 to thechassis body 5231. The example latching members 5236 shown in FIGS. 47and 48 include flexible tabs 5237 defining at least one shoulder 5238.In certain implementations, each latching member 5236 defines a shoulder5238 on each side of the flexible tab 5237. In the example shown, eachflexible tab 5237 generally defines a mushroom shape. In otherimplementations, each flexible tab 5237 generally defines a T-shape.

When the jack modules 5110 are installed on the chassis body 5231, thefront ends of the jack modules 5110 are inserted through the openings5232 of the chassis body 5231 from a rear of the chassis body 5231. Asthe jack module 5110 is being inserted, one of the latching members 5236of the chassis body 5231 cams over the ramped surfaces 5124 of thelatching members 5123 of the jack modules 5110 (see FIG. 47). When thejack module 5110 has been sufficiently inserted in the chassis 5231, thelatching member 5236 of the chassis body 5231 snaps over the latchingmembers 5123 of the jack module 5110 so that the shoulders 5238 of thechassis latching member 5236 abut against shoulders 5125 of the jacklatching member 5123 (see FIG. 48).

FIG. 51 shows a cross-sectional view of an example plug 5002 insertedwithin an assembled patch panel 5200. The plug 5002 extends through thefascia opening 5252, the frame opening 5242, and into the socket 5112 ofthe jack module 5110 mounted to the chassis 5230. The storage membercontacts 5034 of the plug 5002 depress the second contacts 5146 of themedia reading interface 5145 to lift the second contacts 5146 off theshorting pin 5155. The second printed circuit board 5165 is electricallyconnected to the second contacts 5146 is configured to sense when thesecond contacts 5146 are no longer being shorted together by the pin5155.

One example processing unit 5270 is shown in FIG. 34C. The processingunit 5270 includes at least a first connector 5271 with which theprocessing unit 5270 may be connected to the second printed circuitboard 5270. In accordance with some aspects, certain types of processingunits include guide and/or retaining members that facilitate connectingthe processing units to the printed circuit board 5165. For example, theprocessing unit 5270 includes a retaining member 5274 with which theprocessing unit 5270 may be secured to the patch panel 5200. In certainimplementations, the retaining member 5274 includes a guiding member5275, at least one latching member 5276, and a depression surface 5277.In the example shown, the retaining member 5274 includes two latchingmembers 5276.

The example processing unit 5270 also may include a port (e.g., see port5273 of FIG. 35) configured to receive an electrical cable (e.g., apower cable, a data cable connected to a data network, etc.). In oneimplementation, the port includes an RJ jack (e.g., an RJ-45 jack). Inother implementations, however, the processing unit 5270 may utilizeother types of ports. In certain implementations, the processing unit5270 also includes a second port (e.g., a USB port) at which anothertype of cable may be connected to the processing unit 5270 (e.g., seeport 5273 of FIG. 35).

FIGS. 34 and 50 show one example support member 5260 suitable for usewith the patch panel 5200. The support member 5260 includes a body 5261having arms 5262 that are configured to attach to the patch panel 5200.For example, in some implementations, the arms 5262 may attach to thesecond housing part 5220 of the patch panel 5200 (e.g., to the chassis5230). In other implementations, the arms 5262 may attach to groundingmodules 5209 attached to the patch panel 5200 (e.g., see FIG. 52). Inone implementation, the arms 5262 are unitary with the body 5261 of thesupport member 5260.

As shown in FIG. 34C, the body 5261 of the support plate 5260 includes aretention section 5264 at which the processing unit 5270 may be securedto the support plate 5260. For example, in some implementations, thesupport plate 5260 defines a slot 5265 at the retention section 5274that is configured to receive the guide member 5275 of the retainingprocessing unit 5270. The body 5261 of the support plate 5260 also maydefine openings or slots 5266 that are configured to receive thelatching members 5276 of the retaining member 5274 of the processingunit 5270. In some implementations, the processing unit 5270 is latchedto the support plate 5260 by sliding the processing unit 5270 forwardlyrelative to the support plate 5260.

In accordance with some implementations, the support plate 5260 definesa manager. In some such implementations, the body 5261 defines one ormore slots 5263 at which cables (e.g., cables terminating at the jackmodules 5110) can be secured with cable ties or other retention members.In other implementations, the body 5261 may include one or more raisedtabs at which the cable ties or other retention members may be fastened.For example, one example implementation of a suitable cable manager bodyis shown in FIG. 55E and will be described in more detail herein.

FIGS. 52-60 show another example patch panel 5400 including anotherexample fascia 5450 mounted to another example frame 5440. The frame5440 secures to another example chassis 5430 to enclose media readinginterfaces 5145 mounted to the second printed circuit board 5165. Endcaps 5480 pivotally mount to the chassis 5450 to cover the mountingsections of the frame 5440.

A second example processing unit 5470 including a processor (e.g.,processor 206, 217 of FIG. 2) suitable for attachment to the patch panel5400 is shown in FIG. 55. The second example processing unit 5470includes a first connector 5471 that connects the processing unit 5470to the second printed circuit board 5165. The second processing unit5470 also include a port 5472 configured to receive an electrical cable(e.g., a power cable, a data cable connected to a data network, etc.).In one implementation, the port 5472 includes an RJ jack (e.g., an RJ-45jack). In other implementations, however, the processing unit 5470 mayutilize other types of ports. In certain implementations, the processingunit 5470 also includes a second port (e.g., a USB port) 547′ at whichanother type of cable may be connected to the processing unit 5470.

As shown in FIG. 55, the processing unit 5470 also may include retainingmembers 5474 extending outwardly from sides of the processing unit 5470.In some implementations, the retaining members 5474 are located towardsthe rear end of the processing unit 5470. In other implementations, theretaining members 5474 may be located at an intermediate position alongthe sides of the processing unit 5470. Each retaining member 5474defines a camming surface 5475 and at least one retention tab 5476. Inthe example shown, each guide member 5474 includes an upwardly extendingretention tab 5476 and a downwardly extending retention tab 5476.

The processing unit 5470 also may include guide members 5477 on one orboth sides of the processing unit 5470. In some implementations, theguide members 5477 include one or more rails that extend at leastpartially between the front and rear of the processing unit 5470. Incertain implementations, the guide members 5477 also include a stop 5478at an end of the rail. In the example shown, the stop 5478 is located atan intermediate position between the front and rear of the processingunit 5470. The stop 5478 extends generally orthogonally from the end ofthe rail 5477. In one implementation, the guide members 5477 also mayinclude a forward stop 5479.

A second example cable manager 5460 suitable for use with the patchpanel 5400 (see FIG. 53). The cable manager 5460 includes a body 5461attached to the patch panel 5400. The body 5461 of the manager 5460defines one or more slots 5463 at which cables (e.g., cables terminatingat the jack modules 5110) can be secured with cable ties or otherretention members. In some implementations, the body 5461 of the manager5460 may include raised tabs in place of or in addition to the slots5463.

In some implementations, the body 5461 extending between two arms 5462that are configured to attach to the patch panel 5400. For example, insome implementations, the arms 5462 may attach to a second housing partof the patch panel 5400 (e.g., to the chassis 5430). In otherimplementations, the arms 5462 may attach to grounding modules 5409attached to the patch panel 5400 (e.g., see FIG. 52). In oneimplementation, the arms 5462 are unitary with the body 5461 of thecable manager 5460.

Certain types of cable managers 5460 also may be configured to organizeand/or secure cables routed to the processing unit 5470 when theprocessing unit 5470 is connected to the patch panel 5400. In someimplementations, the example cable manager 5460 includes a support plate5464 that is spaced from the body 5461 of the manager 5460. In theexample shown, the support plate 5464 is generally parallel to themanager body 5461. In certain implementations, the support plate 5464includes one or more slots or raised tabs 5465 at which one or morecables may be secured to the support plate 5464 using cable ties orother fasteners. For example, cables mounted to the processing unit 5470may be secured to the support plate 5464 using the raised tabs 5465.

Certain types of cable managers 5460 also may be configured to supportand/or retain the processing unit 5470 when the processing unit 5470 isconnected to the patch panel 5400. In some implementations, the cablemanager 5460 includes one or more retaining arms 5500 that releasablysecure to the processing unit 5470 to the patch panel 5400. For example,the cable manager 5460 may include two spaced retaining arms 5500 thatretain the retaining members 5474 at opposite sides of the processingunit 5470. In certain implementations, each retaining arm 5500 isconfigured to flex or pivot relative to the patch panel 5400.

As shown in FIG. 56, each retaining arm 5500 includes an elongatedmember 5510 extending between a mounting section 5520 and a handle 5540.In certain implementations, the elongated member 5510 defines a guidingsurface 5515 that facilitates sliding the processing unit 5470 towardthe printed circuit board 5165. The mounting section 5520 of the arm5500 defines a pivot opening 5522 through which a fastener can extend topivotally mount the arm 5500 to the support plate 5464. In certainimplementations, the arm 5500 includes one or more tabs 5524 that extendoutwardly from the mounting section 5520. In the example shown, the arm5500 includes two spaced tabs 5524.

A retaining section 5530 is provided on the arm 5500 at a locationspaced from the mounting section 5520. In the example shown, theretaining section is provided adjacent the handle 5540. The retainingsection 5530 includes at least a first flange 5542 extending outwardlyfrom the elongated member 5510. In the example shown, first and secondflanges 5532 extend outwardly from opposite sides of the elongatedmember 5510. In one implementation, the first and second flanges 5532extend generally parallel to each other. Each flange 5532 defines anopening or slot 5535 that is sized and configured to receive a retentiontab 5476 of the processing unit 5470 (see FIGS. 52-54).

As shown in FIGS. 59-60, each of the arms 5500 is configured to pivotrelative to the support plate 5474. In some implementations, the supportplate 5474 includes inner stops 5476 and outer stops 5477 that defineinhibit pivoting of the arms 5500 beyond a particular range of movement.For example, the inner and outer stops 5476, 5477 may inhibit movementof the arms 5500 beyond where the handle 5540 of each arm 5500 would beaccessible to a user. In the example shown in FIGS. 59-60, a first arm5500 is shown in a first position adjacent the inner stop 5476 and asecond arm 5500 is shown in a second position adjacent the outer stop5477.

To mount the processing unit 5470 to the second printed circuit board5165 of the second patch panel 5400, a user moves the arms 5500 towardthe second position. The user then slides the processing unit 5470toward the second printed circuit board 5165. When the processing unit5470 is slid sufficiently forward, the stop 5478 on the processing unit5470 contacts the tabs 5524 of the arms 5500. Continuing to slide theprocessing unit 5470 forward applies a force to the tabs 5524, whichcauses the arms 5500 to pivot toward the first position. Pivoting thearms 5500 to the first position causes the retaining sections 5530 ofthe arms to contact the retaining members 5574 on the processing unit.For example, the slots 5535 of the retaining flanges 5532 of the arms5500 may receive the tabs 5476 of the retaining members 5474 of theprocessing unit 5470.

To release the second processing unit 5470 from the patch panel 5400, auser pulls the retaining arms 5500 (e.g., via the grip portions 5540)away from the processing unit 5470. Pivoting the arms 5500 toward thesecond position causes the tabs 5524 of the arms 5500 to apply alevering force to the stops 5478 of the processing unit 5470. In someimplementations, the levering force applied to the stops 5478 may besufficient to disconnect the processing unit 5470 from the secondprinted circuit board 5165 (e.g., even when a sufficient grippingsurface of the processing unit 5470 is not available to the user).Indeed, in some implementations, the levering force applied to the stops5478 is sufficient to slide the processing unit 5470 rearwardly of thepatch panel 5400.

FIGS. 61-71 show a third example patch panels 5300 at which multiplejack modules 5110 can be assembled. The third example patch panel 5300includes two rows of front cable ports 5305 at which the sockets 5112 ofthe jack modules 5110 are accessible. In some implementations, the jackmodules 5110 of the second row are oriented upside-down relative to thejack modules 5110 of the first row (e.g., see FIGS. 61-62).

In certain implementations, the media reading interfaces 5145 associatedwith the jack modules 5110 of the second row are oriented upside-downrelative to the media reading interfaces 5145 associated with the jackmodules 5110 of the first row. For example, a first row of media readinginterfaces 5145 may be mounted to a first edge of the second printedcircuit board 5165 and a second row of media reading interfaces 5145 maybe mounted to a second edge of the second printed circuit board 5165(FIG. 64).

In some implementations, the patch panel 5300 shown in FIG. 61 is sizedat 2 RU. In one example implementation, the patch panel 5300 shown inFIG. 61 defines forty-eight cable ports 5305 with twenty-four ports ineach row. In certain implementations, the patch panel 5300 shown in FIG.61 is sized to be smaller than 2 RU. In certain implementations, thepatch panels 5200, 5400 are sized at 1 RU and define twenty-four frontports 5205, 5405 each. In other implementations, however, each patchpanel 5200, 5300, 5400 may define greater or fewer front ports.

The third patch panel 5300 includes mounting members 5306. The mountingmember 5306 defines one or more openings 5307 through which a fastenermay extend to secure the third patch panel 5300 to rails or posts of aframe, a rack, a cabinet, or other telecommunications equipmentstructures. End caps can be installed over the mounting members 5306. Inone implementation, the end caps may be larger versions of the end caps5280 shown in FIGS. 37-39. In other implementations, the end caps may beconfigured to snap-fit, friction-fit, or otherwise secure over themounting members 5306 to cover the openings 5307.

In some implementations, the third patch panel 5300 includes a firsthousing part 5310 and a second housing part 5320 (see FIG. 61). Thefirst housing part 5310 defines the front ports 5305. In someimplementations, the first housing part 5310 includes a frame 5340. Incertain implementations, the first housing part 5310 also includes afascia 5350 that is removeably coupled to the frame 5340. In certainimplementations, the third patch panel 5300 also includes a groundingconnection. The grounding connection may connect to the shields 5134 ofthe jack modules 5110 and/or to the second printed circuit board 5165.

The second housing part 5320 includes at least one or more jack modules5110 mounted to a chassis arrangement 5330. In certain implementations,the second housing part 5320 also includes one or more media readinginterfaces 5145. In one implementation, the third patch panel 5300 hasthe same number of jack modules 5110 and media reading interfaces 5145.In other implementations, the third patch panel 5300 has more jackmodules 5110 than media reading interfaces 5145. For example, in oneimplementation, the third patch panel 5300 may have twice as many jackmodules 5110 than media reading interfaces 5145. In otherimplementations, the third patch panel 5300 may include more mediareading interfaces 5145 than jack modules 5110. For example, in certainimplementations, each jack module 5110 may define two plug sockets. Insuch implementations, each plug socket may have its own media readinginterface 5145.

In some implementations, the media reading interfaces 5145 are mountedto a printed circuit board 5165. Multiple media reading interfaces 5145mount over at least a first edge of the second printed circuit board5165. In the example shown in FIGS. 61 and 64, multiple media readinginterfaces 5145 mount over different (e.g., opposite) edges of thesecond printed circuit board 5165. Each media reading interface 5145also is connected to at least one jack module 5110. The second printedcircuit board 5165 in installed at the third patch panel 5300. Forexample, in FIG. 61, the second printed circuit board 5165 is configuredto be held between the first housing part 5310 and the second housingpart 5320.

In some implementations, the first housing part 5310 is fastened to thesecond housing part 5320. In the example shown, the frame 5340 definesone or more first openings 5312 (FIG. 63), the second printed circuitboard 5165 defines one or more second openings 5322 (FIG. 64), and thechassis arrangement 5230 defines one or more third openings 5324 (FIGS.65-66). One or more fasteners (e.g., screws, bolts, etc.) 5315 areconfigured to extend through the first, second, and third openings 5312,5322, 5324 to secure the second printed circuit board 5165 between theframe 5340 and the chassis arrangement 5330. In certain implementations,the fastener 5315 is configured to extend through a spacer 5318positioned between the frame 5340 and the second printed circuit board5165.

In the example shown, a threaded fastener 5315 is configured to extendthrough the openings 5312, 5322, 5324. In some implementations, thethreaded fastener 5315 is configured to screw directly into the chassisarrangement 5330 (e.g., into the passages 5324 defined in the chassisarrangement 5330). In other implementations, however, the threadedfastener 5315 is configured to screw into a threaded insert 5325. Insome such implementations, the threaded insert 5325 may abut against aportion of the chassis arrangement 5330 from a rear of the chassisarrangement 5330. For example, the threaded insert 5325 may mount atleast partially within the passage 5324 defined in the arrangement 5330and abut against a forward or intermediate surface of the arrangement5330.

One example implementation of a frame 5340 is shown in FIG. 63. Theframe 5340 includes a frame body 5341 defining at least one opening 5342through which a plug 5002 can access a socket 5112 of a jack module5110. In certain implementations, the openings 5342 are sufficientlylarge to enable the front of both the jack module 5110 and the mediareading interface 5145 to be viewing from a front of the frame 5340 whenthe first and second housing parts 5310, 5320 are mounted together. Forexample, the viewing channel 5153 of the media reading interface 5145may be viewing through the frame opening 5342.

In certain implementations, the frame body 5341 defines upper and lowerbent flanges 5343 that wrap around portions of the second housing part5320 to aid in retaining the first and second housing parts 5310, 5320.In certain implementations, the lower flange 5343 may aid in retainingthe second printed circuit board 5165 within the patch panel 5300. Forexample, the lower bent flange 5343 of the frame body 5341 may extendover a bottom of the second circuit board 5165 to hold the secondcircuit board 5165 within the channel 5150 defined in the second mediareading interface (e.g., see FIG. 71)

As noted above, the frame body 5341 also defines openings 5312 throughwhich fasteners (e.g., screws, bolts, rivets, etc.) 5315 may be insertedto secure the first housing part 5310 to the second housing part 5320.In some implementations, the frame body 5341 also defines openings toaccommodate components mounted to the second housing part 5320. Forexample, the frame body 5341 may define openings 5346, 5347 toaccommodate a cable port 5166 and light indicators 5167, respectively,as will be described in more detail herein.

In some implementations, the frame body 5341 defines the mountingmembers 5206. For example, side flanges of the frame 5341 define theopenings 5307 through which fasteners may be extended. In otherimplementations, separate mounting members 5306 may connect to the framebody 5341. In other implementations, the mounting members 5306 may bedefined by the fascia 5350. In still other implementations, the mountingmembers 5306 may connect to the second housing part 5320 (e.g., to thechassis 5330).

The frame body 5341 also is configured to receive the fascia 5350. Insome implementations, the frame body 5341 defines openings 5344configured to receive retaining members 5358 of the fascia 5350. Inother implementations, the frame body 5341 may define retaining membersthat fit into openings defined in the fascia 5350. In certainimplementations, the frame body 5341 also includes tabs 5345 that extendforwardly from some of the openings 5342 to be received in slots definedin the fascia 5350 to aid in aligning and installing the fascia 5350 onthe frame 5340.

One example implementation of a fascia 5350 is shown in FIG. 62. Thefascia 5350 includes a fascia body 5351 defining a plurality of openings5352 that align with the openings 5342 of the frame body 5341 to provideaccess to the jack module socket 5112 from the front 5301 of the patchpanel 5300. In some implementations, the openings 5352 of the fasciabody 5351 are smaller than the openings 5342 of the frame body 5341. Incertain implementations, the openings 5352 of the fascia body 5351define keyways 5353 for the plugs 5002. They keyways 5353 of the fasciabody 5351 are oriented to align with the cutouts 5113 of the jackmodules 5110 when the first and second housing parts 5310, 5320 aremounted together.

In some implementations, the fascia body 5351 includes tabs 5354 thatextend rearward from the fascia body 5351. In the example shown, thetabs 5354 generally align with the openings 5352. In otherimplementations, however, the fascia body 5351 may include greater orfewer tabs 5354. The tabs 5354 extend over the upper and lower bendflanges 5343 of the frame body 5341 when the fascia 5350 is mounted tothe frame 5340. In one implementation, the tabs 5354 friction-fit overthe flanges 5343 of the frame to aid in retaining the fascia 5350 to theframe 5340. In certain implementations, some of the tabs 5354 defineopenings, cutouts 5355, or inner protrusions that may aid in retainingthe fascia 5350 to the frame 5340.

As noted above, the fascia body 5351 also includes retaining members5358 to secure the fascia body 5351 to the frame body 5341. In someimplementations, the fascia body 5351 includes at least one retainingmember 5358 at each side of the fascia body 5351. In otherimplementations, the fascia body 5351 includes multiple retainingmembers 5358 at each side of the fascia body 5351. In someimplementations, the retaining members 5358 may secure (e.g., latch,press-fit, snap-fit, etc.) to the frame body 5341 via latching openings5344. In other implementations, the retaining members 5358 may extendthrough the openings 5344 and secure to the chassis 5330 of the secondhousing part 5320.

In some implementations, the fascia body 5351 also defines openings toaccommodate components mounted to the second housing part 5320. Forexample, the fascia body 5351 may define openings 5356, 5357, 5359 toaccommodate a cable port 5166 and light indicators 5167 of the secondprinted circuit board 5165. One example implementation of a printedcircuit board 5165 including a cable port 5166 and light indicators 5167will be described in more detail herein.

One example chassis arrangement 5330 is shown in FIGS. 65-66. Thechassis arrangement 5330 includes a first chassis body 5331 and a secondchassis body 5331′ that are configured to attach to the frame 5340. Inthe example shown, each chassis body 5331, 5331′ defines a recess 5335,5335′ that cooperate to define a passage through which a processing unit(e.g., processing unit 5270 of FIG. 34C, processing unit 5270′ of FIG.55, etc.) may extend to connect to the second printed circuit board5165.

In some implementations, some of the openings 5322 through which thefasteners pass to attach the chassis arrangement 5330 to the frame 5340are defined in the first chassis body 5331 and others of the openings5322 are defined in the second chassis body 5331′. For example, thefirst chassis body 5331 shown in FIG. 65 defines three passages 5322 oneither side of the recess 5335 and the second chassis body 5331′ shownin FIG. 66 defines three passages 5322 on either side of the recess5335′. The passages 5322′ defined by the second body 5331′ are laterallyoffset from the passages 5322 defined by the first body 5331. In certainimplementation, the first and second bodies 5331, 5331′ definecomplementary protrusions and recesses that fit together when thechassis bodies 5331, 5331′ are mounted to the frame 5340. In oneimplementation, the passages 5322 are defined in the protrusions (e.g.,see FIGS. 65-66).

Each chassis body 5331, 5331′ defines openings 5332, 5332′ through whichthe jack modules 5110 can be mounted to the chassis bodies 5331, 5331′.In the example shown, each chassis body 5331, 5331′ defines a row ofopenings 5332, 5332′. In certain implementations, each chassis body5331, 5331′ includes a mounting member 5333, 5333′ located within eachopening 5332, 5332′. In the example shown in FIGS. 65 and 66, eachmounting member 5333, 5333′ includes a generally T-shaped body definingchannels 5334, 5334′ on either side. Each mounting member 5333, 5333′ isconfigured to aid in retaining one of the jack modules 5110 in theopening 5232.

In certain implementations, the jack modules 5110 are installed on thechassis bodies 5331, 5331′ from the rear side of the chassis arrangement5330 (e.g., FIG. 61). The jack module 5110 slides into the opening 5332,5332′ with the guide members 5127 of the jack module 5110 (see FIGS. 17and 19) positioned on either side of the mounting member 5333, 5333′. Inone implementation, the latching members 5116 of the jack module 5110slide within the channels 5334, 5334′ defined by the mounting member5333, 5333′.

In some implementations, each media reading interface 5145 is mounted toa corresponding jack module 5110 after the jack module 5110 is mountedto the chassis arrangement 5330. In other implementations, each mediareading interface 5145 is installed on the second printed circuit board5165 to form a board arrangement 5389 (FIG. 64). The board arrangement5389 can be mounted to the chassis arrangement 5330 before or after thejack modules 5110 are mounted to the chassis arrangement 5330.

In some implementations, each chassis body 5331, 5331′ includes one ormore latching members 5336 that aid in retaining the jack modules 5110to the chassis body 5331, 5331′. The example latching members 5336 shownin FIG. 65 include flexible tabs 5337 defining at least one shoulder5338. In certain implementations, each latching member 5336 defines ashoulder 5338 on each side of the flexible tab 5337. In the exampleshown, each flexible tab 5337 generally defines a mushroom shape. Inother implementations, each flexible tab 5337 generally defines aT-shape.

When the jack modules 5110 are installed on the chassis arrangement5330, the front ends of the jack modules 5110 are inserted through theopenings 5332, 5332′ of the chassis bodies 5331, 5331′ from a rear ofthe chassis bodies 5331, 5331′. As the jack module 5110 is beinginserted, one of the latching members 5336 of the chassis body 5331,5331′ cams over the ramped surfaces 5124 of the latching members 5123 ofthe jack modules 5110 (see FIG. 67). When the jack module 5110 has beensufficiently inserted in the chassis body 5331, 5331′, the latchingmember 5336 of the chassis body 5331, 5331′ snaps over the latchingmembers 5123 of the jack module 5110 so that the shoulders 5338 of thechassis latching member 5336 abut against shoulders 5125 of the jacklatching member 5123 (see FIG. 67).

In accordance with some aspects, the second printed circuit board 5165is configured to receive a processing unit (e.g., processing unit 5270of FIG. 34C, processing unit 5470 of FIG. 55).

In accordance with some aspects, the cable manager 5360 is configuredsimilarly to the cable manager 5260 of the patch panel 5200 (see FIGS.67-70). The cable manager 5360 includes at least one rail 5361 thatdefines slots 5363 at which cable may be secured to the rail 5361 usingcable ties or other fasteners. The cable manager 5360 also includes arms5362 that secure the rail 5361 to the patch panel 5300. In someimplementations, the cable manager 5360 includes multiple rails 5361,5361′ each defining slots 5363, 5363′ and including arms 5362, 5362′ tosecure the rails 5361, 5361′ to the patch panel 5300.

One example cable manager 5360 includes a first rail 5361 (FIG. 69) anda second rail 5361′ (FIG. 70). The first rail 5361 also defines aretention section 5364 that is configured to receive the processing unit5270. The retention surface 5364 defines a recess 5365 through which theguide member 5275 of the processing unit 5270 can extend to connect tothe second printed circuit board 5165 of the patch panel 5300. Theretention section 5364 also includes openings 5366 at which retainingmembers 5276 of the processing unit 5270 latch to secure the processingunit 5270 to the patch panel 5300. In the example shown, the retentionsection 5364 also includes raised tabs 5367 at which cables routed tothe processing unit 5270 may be managed

FIGS. 72-78 show a fourth example patch panel 5600. The fourth examplepatch panel 5600 includes a fascia 5650 (FIGS. 73-75), a frame 5640(FIGS. 76-78), and a chassis 5630 (see FIG. 72). A second printedcircuit board 5165 is mounted between the frame 5640 and the chassis5630. For example, the fourth patch panel 5600 can be assembled asdescribed above with respect to any of patch panels 5200, 5300, and5400. A grounding arrangement 5609 (FIG. 78) connects to the frame 5640.

A cable manager 5660 is configured to mount to the fourth patch panel5600 (e.g., to a grounding plate arrangement 5609 of the patch panel5600). In certain implementations, the cable manager 5660 includesmultiple rails 5661 at which cables can be secured (e.g., using cableties). In the example shown, the cable manger 5560 includes a rail 5661,5661′ for each row of jack modules 5110. In some implementations, thecable manager 5660 utilizes the retaining arms 5500 described above withrespect to FIGS. 52-60.

One example implementation of a fascia 5250 is shown in FIG. 73-75. Thefascia 5650 includes a fascia body 5651 defining a plurality of openings5652 through which a plug 5002 can access a socket 5112 of a jack module5110 from the front of the patch panel 5600. In some implementations,the openings 5652 of the fascia body 5651 are smaller than the openings5642 of the frame body 5641. In certain implementations, the openings5652 of the fascia body 5651 define keyways 5653 for the plugs 5002.They keyways 5653 of the fascia body 5651 are oriented to align with thecutouts 5113 of the jack modules 5110 when the patch panel 5600 isassembled.

In some implementations, the fascia body 5651 includes tabs 5654 thatextend rearward from the fascia body 5651. In the example shown, thetabs 5654 generally align with the openings 5652. In otherimplementations, however, the fascia body 5651 may include greater orfewer tabs 5654. The tabs 5654 extend over the upper and lower bendflanges 5643 of the frame body 5641 when the fascia 5650 is mounted tothe frame 5640. In one implementation, the tabs 5654 friction-fit overthe flanges 5643 of the frame to aid in retaining the fascia 5650 to theframe 5640. In certain implementations, some of the tabs 5654 defineopenings, cutouts, or inner protrusions that may aid in retaining thefascia 5650 to the frame 5640 (see FIG. 74).

As noted above, the fascia body 5651 also includes retaining members5658 to secure the fascia body 5651 to the frame body 5641. In someimplementations, the fascia body 5651 includes multiple retainingmembers 5658 spaced along a one side of the fascia body 5651. In theexample shown, the fascia body 5651 includes multiple hooks 5658 spacedalong a bottom of the fascia body 5651. The retaining members 5658extend through the frame body 5641 and latch in the openings 5644. Incertain implementations, the top of the fascia body 5651 may beconfigured to snap, pivot, or otherwise secure to the top of the frame5640. Of course, this attachment mechanism can be used between any ofthe frames and fascias disclosed herein.

In some implementations, the fascia body 5651 also defines openings toaccommodate components mounted to the chassis 5630 or second printedcircuit board 5165. For example, the fascia body 5651 may defineopenings 5656, 5657, 5659 to accommodate a cable port 5166 and lightindicators 5167 of the second printed circuit board 5165. One exampleimplementation of a printed circuit board 5165 includes a cable port5166, a first light indicator, and three additional light indicators5167.

Labels may be installed on the fascia body 5651. In someimplementations, labels are installed on a front of the fascia body5651. For example, labels may be glued, latched, or otherwise secured toa front of the fascia body 5651. In other implementations, however,labels may be installed behind a clear or opaque fascia body 5651. Incertain implementations, one or more label holders 5290 (FIGS. 40-41)may be mounted to back of the fascia body 5651. For example, the labelholder may be mounted within one or more tracks 5655 (FIG. 75).

One example implementation of a frame 5640 is shown in FIGS. 76-78. Theframe 5640 includes a frame body 5641 defining at least one opening 5642that align with the openings 5642 of the frame body 5241 to provideaccess to a socket 5112 of a jack module 5110. In certainimplementations, the openings 5642 are sufficiently large to enable thefront of both the jack module 5110 and the media reading interface 5145to be viewing from a front of the frame 5640 when the frame 5640 andchassis 5630 are mounted together. For example, the viewing channel 5153of the media reading interface 5145 may be viewing through the frameopening 5642.

In certain implementations, the frame body 5641 defines upper and lowerbent flanges 5643 that wrap around portions of the chassis 5630 to aidin retaining the second printed circuit board 5165 within the patchpanel 5600. For example, the lower bent flange 5643 of the frame body5641 may extend over a bottom of the second circuit board 5165 to holdthe second circuit board 5165 within the channel 5150 defined in thesecond media reading interface (e.g., see FIG. 51).

As noted above, the frame body 5641 also defines openings 5612 throughwhich fasteners (e.g., screws, bolts, rivets, etc.) may be inserted tosecure the frame 5640 to the chassis 5630. In some implementations, theframe body 5641 also defines openings to accommodate components mountedto the chassis 5630 and second printed circuit board 5165. For example,the frame body 5641 may define openings 5646, 5647 to accommodate acable port 5166 and light indicators 5167, respectively, as describedherein.

In some implementations, the frame body 5641 defines the mountingmembers 5606. For example, side flanges of the frame 5641 define theopenings 5607 through which fasteners may be extended. In otherimplementations, separate mounting members 5606 may connect to the framebody 5641. In other implementations, the mounting members 5606 may bedefined by the fascia 5650. In still other implementations, the mountingmembers 5606 may connect to the chassis 5630.

The frame body 5641 also is configured to connect to the fascia 5650. Insome implementations, the frame body 5641 defines openings 5644configured to receive retaining members 5658 of the fascia 5650 (FIG.78). In other implementations, the frame body 5641 may define retainingmembers that fit into openings defined in the fascia 5650. In certainimplementations, the frame body 5641 also includes tabs 5645 that extendforwardly from some of the openings 5642 to be received in slots definedin the fascia 5650 to aid in aligning and installing the fascia 5650 onthe frame 5640.

As shown in FIGS. 74 and 78, end caps 5680 may be mounted over the sideflanges of the frame 5641 to cover the mounting members 5606. In theexample shown, each end cap 5680 includes a body that is sized andshaped to cover the front of one side flange of the frame 5641. Each endcap 5680 also includes mounting members by which the end cap body isattached to the patch panel 5600. In some implementations, the mountingmembers attach to the fascia body 5651 (FIG. 74).

A number of embodiments of the invention defined by the following claimshave been described. Nevertheless, it will be understood that variousmodifications to the described embodiments may be made without departingfrom the spirit and scope of the claimed invention. Accordingly, otherembodiments are within the scope of the following claims.

The invention claimed is:
 1. A jack module comprising: a jack body having a front, a rear, a first end, a second end, a first side, and a second side, the jack body defining a socket configured to receive a plug from the front of the jack body, the second end of the jack body defining a cutout region that provides access to the socket through the second end of the jack body, the jack body including guides that define external guide channels at the first end of the jack body, each of the guides defining a ramped surface at a front end; a plurality of plug contacts positioned within the jack body, at least a portion of the plug contacts extending into the socket from the first end of the jack body; and a plurality of terminating contacts positioned within the jack body, the terminating contacts being electrically connected to the plug contacts, the terminating contacts being configured to terminate at least one electrical media segment.
 2. The jack module of claim 1, further comprising a printed circuit board positioned within the jack body, the printed circuit board electrically connecting the plug contacts and the terminating contacts.
 3. The jack module of claim 2, wherein the terminating contacts include insulation displacement contacts.
 4. The jack module of claim 2, wherein the printed circuit board extends parallel to an insertion axis of the socket.
 5. The jack module of claim 1, wherein the jack module includes at least one plug latching member positioned within the cutout region, each plug latching member including a camming surface and a shoulder.
 6. The jack module of claim 1, wherein the first end of the jack body opposes the second end of the jack body.
 7. The jack module of claim 1, wherein the jack module includes first and second guide channels positioned at the second end of the jack module on either side of the cutout region.
 8. The jack module of claim 1, wherein each guide includes a wing extension, wherein the wing extensions extend outwardly from the first and second sides of the jack body.
 9. The jack module of claim 1, wherein the jack body includes a panel latching arrangement disposed between the guides.
 10. The jack module of claim 9, wherein the panel latching arrangement includes at least a first latch member having a ramped surface and a shoulder.
 11. The jack module of claim 10, wherein the latching arrangement includes two latch members separated by a gap, each latch member defining a ramped surface at one end and a shoulder at the opposite end.
 12. The jack module of claim 1, wherein the plug contacts are first plug contacts, and further comprising a plurality of second plug contacts having first sections that extend through the cutout region of the jack body and into the socket, the second plug contacts being electrically isolated from the first plug contacts.
 13. The jack module of claim 12, wherein the second plug contacts are coupled to a media reading interface housing that is coupled to the second end of the jack module.
 14. The jack module of claim 13, wherein the media reading interface housing has a top, a bottom, a front, a rear, a first side, and a second side, the media reading interface housing defining a channel configured to receive a printed circuit board, the media reading interface housing also including guides at the top of the media reading interface housing, the guides being configured to fit within the external guide channels of the jack body to facilitate mounting the media reading interface housing to the jack body.
 15. The jack module of claim 13, wherein the media reading interface housing provides presence sensing for the jack module.
 16. The jack module of claim 1, wherein the jack body defines at least one rib at each of the first and second sides at the first end of the jack body.
 17. The jack module of claim 16, further comprising a strain relief device including a spring clip having arms configured to mount to the ribs.
 18. The jack module of claim 16, wherein the jack body defines a plurality of ribs at the first and second sides of the jack body. 